Machine status

System overview

Top BOINC processes

top - 15:45:01 up 3 days, 16:47,  2 users,  load average: 5.68, 5.66, 5.83
Tasks: 523 total,   7 running, 516 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.7 us,  1.4 sy, 49.3 ni, 48.6 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem : 128742.9 total, 104063.8 free,   7178.3 used,  18737.5 buff/cache     
MiB Swap: 102400.0 total, 102400.0 free,      0.0 used. 121564.6 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
1018604 boinc     39  19  687492 683980   5048 R 146.2   0.5  76:47.12 hsgamma+
1018702 boinc     39  19  686900 683644   5148 R 146.2   0.5  76:21.66 hsgamma+
1023184 boinc     39  19  687488 683836   4972 R 146.2   0.5  44:01.63 hsgamma+
1028520 boinc     39  19  687496 683836   5072 R 146.2   0.5   7:23.57 hsgamma+
1026700 boinc     39  19  686900 683556   5088 R 138.5   0.5  19:48.73 hsgamma+
1029250 boinc     39  19  686900 683452   5084 R 138.5   0.5   1:42.85 hsgamma+
   1762 boinc     30  10  194516  24368  15876 S   0.0   0.0   8:17.15 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
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinuninitialized 0%2025-04-17
einsteinexecuting 69%2025-04-17
einsteinexecuting 68%2025-04-17
einsteinexecuting 39%2025-04-17
einsteinexecuting 17%2025-04-17
einsteinexecuting 6%2025-04-18
einsteinexecuting 1%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-04T15:45:01 +0200