Machine status

System overview

Top BOINC processes

top - 23:00:01 up 2 days,  3:38,  1 user,  load average: 6.20, 6.11, 6.10
Tasks: 386 total,   7 running, 379 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.7 us,  0.7 sy, 49.6 ni, 48.9 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem : 128740.5 total, 115575.5 free,   7310.4 used,   7085.5 buff/cache     
MiB Swap: 102400.0 total, 102400.0 free,      0.0 used. 121430.1 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
 685546 boinc     39  19  671692 668548   5176 R 109.1   0.5  60:37.61 hsgamma+
 715622 boinc     39  19  671692 668480   5104 R 109.1   0.5  23:24.95 hsgamma+
 619416 boinc     39  19  671692 668616   5244 R 100.0   0.5  91:58.56 hsgamma+
 659054 boinc     39  19  671692 668536   5160 R 100.0   0.5  75:49.49 hsgamma+
 670353 boinc     39  19  671832 668632   5196 R 100.0   0.5  70:28.05 hsgamma+
 715319 boinc     39  19  671692 668476   5104 R 100.0   0.5  24:14.73 hsgamma+
   1667 boinc     30  10  203608  25976  17100 S   0.0   0.0   3:51.60 boinc

Jobs status

ProjectStateProgressDeadline
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinexecuting 74%2025-09-29
einsteinexecuting 61%2025-09-29
einsteinexecuting 57%2025-09-29
einsteinexecuting 49%2025-09-29
einsteinexecuting 19%2025-09-29
einsteinexecuting 18%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29
einsteinuninitialized 0%2025-09-29

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-09-15T23:00:01 +0200