33%
26.02.2014
-sent: 22,334 (total) 0/s (Per-Sec)
pkts-recv: 68,018 (total) 2/s (Per-Sec)
lo
Bytes-sent: 2.55 K (total) 0.00 B/s (Per-Sec)
Bytes
32%
11.02.2016
amount of available RAM: 117,080MB in this case.
Mem used
: Amount of RAM used by the applications: 48,810MB in this case.
Mem free
: Potentially free RAM: 68,270MB in this case.
Mem cached
: RAM
32%
21.08.2012
just two nodes: test1, which is the master node, and n0001, which is the first compute node):
[laytonjb@test1 ~]$ pdsh -w test1,n0001 uptime
test1: 18:57:17 up 2:40, 5 users, load average: 0.00, 0.00
31%
23.03.2016
, if the second bit from the left is flipped from a 0 to a 1 (11011100), the number becomes 220. A simple flip of one bit in a byte can make a drastic difference in its value. Fortunately, ECC memory can detect
31%
30.01.2024
Dell Precision Workstation T7910
Power
1,300W
CPU
2x Intel Xeon Gold E5-2699 V4, 22 cores, 2.4GHz, 55MB of cache, LGA 2011-3
GPU, NPU
n/a*
Memory
31%
20.02.2012
time: 11.79 secs
Data transferred: 2.47 MB
Response time: 0.22 secs
Transaction rate: 35.79 trans/sec
Throughput: 0
31%
27.08.2014
. It is adjusted to terminal size, so each square = 10.00 MiB
The PDF report may be more precise with each pixel=1MB
Heatmap Key: Black (No I/O), white(Coldest),blue(Cold),cyan(Warm),green(Warmer),yellow(Very Warm),magenta(Hot),red(Hottest)
Notice
31%
19.11.2019
Jobs: 1 (f=1): [w(1)][100.0%][w=654MiB/s][w=167k IOPS][eta 00m:00s]
test: (groupid=0, jobs=1): err= 0: pid=1225: Sat Oct 12 19:20:18 2019
write: IOPS=168k, BW=655MiB/s (687MB/s)(10.0GiB/15634msec); 0
31%
30.01.2020
=1): err= 0: pid=1634: Mon Oct 14 22:18:59 2019
write: IOPS=118k, BW=463MiB/s (485MB/s)(10.0GiB/22123msec); 0 zone resets
[ ... ]
Run status group 0 (all jobs):
WRITE: bw=463MiB/s (485MB/s), 463Mi
31%
15.02.2012
rewinddir
0
0
0
0
0
0
0
0
fsync
21
21
21
21
21
22
26
31
lseekm
3
