Machine status

System overview

Top BOINC processes

top - 23:15:02 up  1:05,  1 user,  load average: 6.17, 6.14, 6.06
Tasks: 373 total,   7 running, 366 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us,  0.7 sy, 50.3 ni, 49.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem : 128742.9 total, 124459.2 free,   4731.2 used,    620.9 buff/cache     
MiB Swap: 102400.0 total, 102400.0 free,      0.0 used. 124011.8 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
   2176 boinc     39  19  449392 445540   4956 R 108.3   0.3  64:58.34 hsgamma+
   2178 boinc     39  19  449392 445412   4644 R 108.3   0.3  64:58.11 hsgamma+
   2184 boinc     39  19  449392 445256   4588 R 108.3   0.3  64:58.27 hsgamma+
   2174 boinc     39  19  449980 446096   4676 R 100.0   0.3  64:58.26 hsgamma+
   2175 boinc     39  19  740052 735660   4284 R 100.0   0.6  64:58.00 hsgamma+
   2177 boinc     39  19  449392 445548   4896 R 100.0   0.3  64:58.27 hsgamma+
   1475 boinc     30  10  118588  22008  15736 S   0.0   0.0   0:07.22 boinc

Jobs status

ProjectStateProgressDeadline
einsteinexecuting 62%2025-06-22
einsteinexecuting 71%2025-06-22
einsteinexecuting 40%2025-06-22
einsteinexecuting 40%2025-06-22
einsteinexecuting 40%2025-06-22
einsteinexecuting 40%2025-06-22
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
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
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
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
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-08T23:15:01 +0200