Machine status

System overview

Top BOINC processes

top - 23:00:01 up 3 days, 2 min,  2 users,  load average: 6.47, 6.44, 6.54
Tasks: 566 total,   7 running, 559 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.7 us,  4.6 sy, 47.0 ni, 47.7 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem : 128742.9 total, 103898.9 free,   7576.0 used,  18572.5 buff/cache     
MiB Swap: 102400.0 total, 102400.0 free,      0.0 used. 121167.0 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
 880563 boinc     39  19  687496 684120   5100 R 123.1   0.5   8:58.68 hsgamma+
 853951 boinc     39  19  687492 683964   5092 R 115.4   0.5  28:44.17 hsgamma+
 800906 boinc     39  19  468284 464884   5104 R 107.7   0.4 121:21.16 hsgamma+
 801300 boinc     39  19   33048  29416   5048 R 107.7   0.0 119:47.11 hsgamma+
 844174 boinc     39  19  686900 683492   4996 R 107.7   0.5  70:51.00 hsgamma+
 845254 boinc     39  19  687048 683520   5052 R 107.7   0.5  65:57.96 hsgamma+
   1762 boinc     30  10  194408  24524  15876 S   0.0   0.0   6:39.23 boinc

Jobs status

ProjectStateProgressDeadline
rosettauninitialized 0%2025-03-30
rosettauninitialized 0%2025-03-30
rosettauninitialized 0%2025-03-30
rosettauninitialized 0%2025-03-30
rosettauninitialized 0%2025-03-30
rosettauninitialized 0%2025-03-30
einsteinuninitialized 0%2025-04-17
einsteinexecuting 89%2025-04-17
einsteinexecuting 89%2025-04-17
einsteinexecuting 62%2025-04-17
einsteinexecuting 58%2025-04-17
einsteinexecuting 25%2025-04-17
einsteinexecuting 7%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17

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-04-03T23:00:01 +0200