Machine status

System overview

Top BOINC processes

top - 09:45:01 up 1 day,  6:43,  1 user,  load average: 6.14, 6.16, 6.06
Tasks: 383 total,   7 running, 376 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us,  1.4 sy, 50.0 ni, 48.6 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem : 128742.9 total, 119262.2 free,   6937.3 used,   3779.9 buff/cache     
MiB Swap: 102400.0 total, 102400.0 free,      0.0 used. 121805.6 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
 212031 boinc     39  19  687572 684152   4888 R 109.1   0.5 106:59.08 hsgamma+
 219394 boinc     39  19  687572 684520   5260 R 109.1   0.5  52:46.64 hsgamma+
 219599 boinc     39  19  687572 684304   5076 R 109.1   0.5  51:52.72 hsgamma+
 213102 boinc     39  19  688160 685040   5268 R 100.0   0.5  99:58.02 hsgamma+
 219468 boinc     39  19  683084 679636   4928 R 100.0   0.5  52:36.24 hsgamma+
 221137 boinc     39  19  687572 684240   4980 R 100.0   0.5  40:56.80 hsgamma+
   1482 boinc     30  10  197472  26656  16308 S   0.0   0.0   2:12.36 boinc

Jobs status

ProjectStateProgressDeadline
einsteinuninitialized 0%2025-07-18
einsteinexecuting 84%2025-07-18
einsteinexecuting 78%2025-07-18
einsteinexecuting 41%2025-07-18
einsteinexecuting 41%2025-07-18
einsteinexecuting 40%2025-07-18
einsteinexecuting 31%2025-07-18
einsteinuninitialized 0%2025-07-18
einsteinuninitialized 0%2025-07-18
einsteinuninitialized 0%2025-07-18
einsteinuninitialized 0%2025-07-18
einsteinuninitialized 0%2025-07-18
einsteinuninitialized 0%2025-07-18
einsteinuninitialized 0%2025-07-18
einsteinuninitialized 0%2025-07-18
einsteinuninitialized 0%2025-07-18
einsteinuninitialized 0%2025-07-18
einsteinuninitialized 0%2025-07-18
einsteinuninitialized 0%2025-07-18
einsteinuninitialized 0%2025-07-18
einsteinuninitialized 0%2025-07-18
einsteinuninitialized 0%2025-07-18
einsteinuninitialized 0%2025-07-18
einsteinuninitialized 0%2025-07-18
einsteinuninitialized 0%2025-07-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-07-04T09:45:01 +0200