Machine status

System overview

Top BOINC processes

top - 02:15:01 up 3 days,  3:17,  3 users,  load average: 6.24, 6.18, 6.01
Tasks: 528 total,   7 running, 521 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us,  1.3 sy, 50.3 ni, 48.3 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem : 128742.9 total, 104327.8 free,   7158.8 used,  18492.8 buff/cache     
MiB Swap: 102400.0 total, 102400.0 free,      0.0 used. 121584.2 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
 904589 boinc     39  19  686900 683348   4996 R 100.0   0.5  77:01.65 hsgamma+
 906096 boinc     39  19  686900 683480   5112 R 100.0   0.5  67:25.35 hsgamma+
 906381 boinc     39  19  686900 683392   4972 R 100.0   0.5  65:29.37 hsgamma+
 914031 boinc     39  19  686900 683504   5000 R 100.0   0.5  12:27.49 hsgamma+
 901529 boinc     39  19  686900 683528   4940 R  91.7   0.5  99:23.69 hsgamma+
 913243 boinc     39  19  686900 683236   4828 R  91.7   0.5  16:16.26 hsgamma+
   1762 boinc     30  10  194408  24524  15876 S   0.0   0.0   6:58.59 boinc

Jobs status

ProjectStateProgressDeadline
rosettauninitialized 0%2025-03-30
rosettauninitialized 0%2025-03-30
rosettauninitialized 0%2025-03-30
rosettauninitialized 0%2025-03-30
rosettauninitialized 0%2025-03-30
rosettauninitialized 0%2025-03-30
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinexecuting 88%2025-04-17
einsteinexecuting 68%2025-04-17
einsteinexecuting 59%2025-04-17
einsteinexecuting 57%2025-04-17
einsteinexecuting 14%2025-04-17
einsteinexecuting 10%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18

Appendix

[1] RAM usage is the combination of resident memory in use on one side, and on the other side the use of shared memory, notably allocated to tmpfs-es such as /tmp, or my sbuild overlay. It does not take into account the file cache, as it usually tries as much as possible to take up all the remaining space, and thus is not a good metric to see if something is going wrong.

[ICO]NameLast modifiedSize
[PARENTDIR]Parent Directory  -

Last update: 2025-04-04T02:15:01 +0200