Machine status

System overview

Top BOINC processes

top - 12:15:01 up 7 days, 52 min,  1 user,  load average: 6.01, 5.98, 5.97
Tasks: 386 total,   7 running, 379 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us,  0.7 sy, 50.0 ni, 49.3 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem : 128742.9 total, 104380.4 free,   5645.8 used,  19954.7 buff/cache     
MiB Swap: 102400.0 total, 102400.0 free,      0.0 used. 123097.2 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
2027693 boinc     39  19   23712  20160   5032 R 100.0   0.0 136:49.78 hsgamma+
2028040 boinc     39  19  449392 446004   4960 R 100.0   0.3 134:21.32 hsgamma+
2028430 boinc     39  19  449392 446024   4948 R 100.0   0.3 132:52.50 hsgamma+
2044902 boinc     39  19  449392 445856   4932 R 100.0   0.3   7:47.05 hsgamma+
2030742 boinc     39  19  449392 446100   5012 R  91.7   0.3 115:50.86 hsgamma+
2043067 boinc     39  19  449392 446088   5100 R  91.7   0.3  21:23.74 hsgamma+
   1765 boinc     30  10  272056  27336  16076 S   0.0   0.0  16:42.95 boinc

Jobs status

ProjectStateProgressDeadline
einsteinuninitialized 0%2025-06-21
einsteinuninitialized 0%2025-06-21
einsteinexecuting 89%2025-06-21
einsteinexecuting 89%2025-06-21
einsteinexecuting 88%2025-06-21
einsteinexecuting 77%2025-06-21
einsteinexecuting 14%2025-06-21
einsteinexecuting 5%2025-06-21
einsteinuninitialized 0%2025-06-21
einsteinuninitialized 0%2025-06-21
einsteinuninitialized 0%2025-06-21
einsteinuninitialized 0%2025-06-21
einsteinuninitialized 0%2025-06-21
einsteinuninitialized 0%2025-06-21
einsteinuninitialized 0%2025-06-21
einsteinuninitialized 0%2025-06-21
einsteinuninitialized 0%2025-06-21
einsteinuninitialized 0%2025-06-21
einsteinuninitialized 0%2025-06-22
einsteinuninitialized 0%2025-06-22
einsteinuninitialized 0%2025-06-22
einsteinuninitialized 0%2025-06-22
einsteinuninitialized 0%2025-06-22

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-06-08T12:15:01 +0200