Machine status

System overview

Top BOINC processes

top - 12:00:01 up 16:08,  2 users,  load average: 6.14, 6.10, 6.16
Tasks: 545 total,   7 running, 538 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.7 us,  1.4 sy, 50.7 ni, 47.3 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem : 128742.9 total, 120720.4 free,   5578.2 used,   3596.3 buff/cache     
MiB Swap: 102400.0 total, 102400.0 free,      0.0 used. 123164.7 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
 147929 boinc     39  19  419372 415292   4860 R 100.0   0.3 120:27.54 hsgamma+
 157347 boinc     39  19  419372 415768   5072 R 100.0   0.3  66:44.69 hsgamma+
 164908 boinc     39  19  419376 415468   4940 R 100.0   0.3  35:18.23 hsgamma+
 165034 boinc     39  19  419372 415824   5032 R 100.0   0.3  35:04.80 hsgamma+
 167109 boinc     39  19  418580 414872   4992 R 100.0   0.3  27:01.31 hsgamma+
 171722 boinc     39  19  419168 415412   4984 R 100.0   0.3   5:23.72 hsgamma+
   1771 boinc     30  10  194956  24780  15880 S   0.0   0.0   1:46.40 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-25
einsteinexecuting 87%2025-04-25
einsteinexecuting 48%2025-04-25
einsteinexecuting 25%2025-04-25
einsteinexecuting 25%2025-04-25
einsteinexecuting 19%2025-04-25
einsteinexecuting 3%2025-04-25
einsteinuninitialized 0%2025-04-25
einsteinuninitialized 0%2025-04-25
einsteinuninitialized 0%2025-04-25
einsteinuninitialized 0%2025-04-25
einsteinuninitialized 0%2025-04-25
einsteinuninitialized 0%2025-04-25
einsteinuninitialized 0%2025-04-25
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26
einsteinuninitialized 0%2025-04-26

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-12T12:00:01 +0200