Machine status

System overview

Top BOINC processes

top - 19:45:01 up 3 days, 20:47,  2 users,  load average: 6.09, 6.18, 6.17
Tasks: 544 total,   7 running, 537 sleeping,   0 stopped,   0 zombie
%Cpu(s):  3.8 us,  7.5 sy, 49.7 ni, 39.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem : 128742.9 total, 103244.2 free,   7416.8 used,  19339.5 buff/cache     
MiB Swap: 102400.0 total, 102400.0 free,      0.0 used. 121326.2 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
1053525 boinc     39  19  686900 683700   5112 R 100.0   0.5  68:13.59 hsgamma+
1065631 boinc     39  19  686900 683500   5148 R 100.0   0.5  13:07.77 hsgamma+
1045781 boinc     39  19  468220 464192   5056 R  92.3   0.4 121:56.68 hsgamma+
1046933 boinc     39  19  467108 463680   5092 R  92.3   0.4 115:04.97 hsgamma+
1053409 boinc     39  19  686900 683384   5004 R  92.3   0.5  68:49.03 hsgamma+
1058272 boinc     39  19  686900 683092   4976 R  92.3   0.5  34:55.12 hsgamma+
   1762 boinc     30  10  194516  24368  15876 S   0.0   0.0   8:40.05 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-18
einsteinuninitialized 0%2025-04-18
einsteinexecuting 89%2025-04-18
einsteinexecuting 89%2025-04-18
einsteinexecuting 61%2025-04-18
einsteinexecuting 60%2025-04-18
einsteinexecuting 31%2025-04-18
einsteinexecuting 11%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18
einsteinuninitialized 0%2025-04-18

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-04T19:45:01 +0200