Machine status

System overview

Top BOINC processes

top - 20:15:01 up 3 days, 21:17,  2 users,  load average: 6.09, 6.18, 6.11
Tasks: 549 total,   7 running, 542 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.7 us,  1.3 sy, 49.3 ni, 48.7 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem : 128742.9 total, 102790.4 free,   7861.6 used,  19349.0 buff/cache     
MiB Swap: 102400.0 total, 102400.0 free,      0.0 used. 120881.3 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
1053409 boinc     39  19  686900 683384   5004 R 100.0   0.5  98:05.47 hsgamma+
1058272 boinc     39  19  686900 683196   4976 R 100.0   0.5  64:11.61 hsgamma+
1065631 boinc     39  19  686900 683500   5148 R 100.0   0.5  42:24.30 hsgamma+
1069440 boinc     39  19  686900 683396   5112 R 100.0   0.5  28:04.59 hsgamma+
1070913 boinc     39  19  686900 683100   5092 R 100.0   0.5  21:08.99 hsgamma+
1053525 boinc     39  19  686900 683700   5112 R  91.7   0.5  97:29.99 hsgamma+
   1762 boinc     30  10  194516  24368  15876 S   0.0   0.0   8:43.19 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
einsteinexecuting 87%2025-04-18
einsteinexecuting 86%2025-04-18
einsteinexecuting 56%2025-04-18
einsteinexecuting 37%2025-04-18
einsteinexecuting 24%2025-04-18
einsteinexecuting 18%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
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-04T20:15:01 +0200