Machine status

System overview

Top BOINC processes

top - 11:00:02 up 6 days, 23:37,  1 user,  load average: 6.09, 6.08, 6.03
Tasks: 387 total,   7 running, 380 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 : 128742.9 total, 103904.1 free,   6122.2 used,  19954.6 buff/cache     
MiB Swap: 102400.0 total, 102400.0 free,      0.0 used. 122620.7 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
2024477 boinc     39  19  449392 445676   4820 R  91.7   0.3  87:09.39 hsgamma+
2026413 boinc     39  19  449392 445960   4976 R  91.7   0.3  72:45.54 hsgamma+
2027693 boinc     39  19  449392 445968   5032 R  91.7   0.3  62:31.78 hsgamma+
2028040 boinc     39  19  449392 446004   4960 R  91.7   0.3  60:03.43 hsgamma+
2028430 boinc     39  19  449392 446024   4948 R  91.7   0.3  58:34.53 hsgamma+
2030742 boinc     39  19  449392 446056   5012 R  91.7   0.3  41:32.88 hsgamma+
   1765 boinc     30  10  272056  27208  16076 S   0.0   0.0  16:35.49 boinc

Jobs status

ProjectStateProgressDeadline
einsteinexecuting 58%2025-06-21
einsteinexecuting 48%2025-06-21
einsteinexecuting 41%2025-06-21
einsteinexecuting 39%2025-06-21
einsteinexecuting 38%2025-06-21
einsteinexecuting 27%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-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-08T11:00:01 +0200