34%
21.01.2021
.86–2.66GHz
Jan 2010
Nehalem
Dual-core; 32+32 L1, 256KB L2, 3MB L3; 2.8GHz, two threads per core
Table 2: Supercomputer Processor Progression
Date
Processor
34%
11.02.2016
.40 <- < 71% idle >
0 1.00 0.00 0.37 0.00 0.00 0.06 0.00 0.00 0.00 98.57
1 100.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
2 3.77 0.00
34%
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
34%
11.04.2016
(512 MB) copied, 49.1424 s, 10.4 MB/s
If you want to empty the read and write cache for benchmark purposes, you can do so using:
sync; echo 3 > /proc/sys/vm/drop_caches
Sequential access
34%
25.02.2013
)
01/31/2013 _i686_ (1 CPU)01/31/2013 09:56:01 AM
avg-cpu: %user %nice %system %iowait %steal %idle
14.78 0.38 3.47 2.16 0.00 79.21
Device: rrqm/s wrqm
34%
25.03.2021
, ioengine=libaio, iodepth=32
fio-3.12
Starting 1 process
Jobs: 1 (f=1)
test: (groupid=0, jobs=1): err= 0: pid=5956: Sat Jan 9 16:38:53 2021
read: IOPS=256k, BW=998MiB/s (1047MB/s)(2045MiB/2049msec
34%
30.11.2025
. You can create memory pressure in the system by launching eight RAM hogs:
stress -m 8 --verbose
These tasks malloc 256MB and touch a byte every 4096 bytes, which dirties each memory page and forces
33%
30.01.2020
tottime percall cumtime percall filename:lineno(function)
148/1 0.001 0.000 156.745 156.745 {built-in method builtins.exec}
1 149.964 149.964 156.745 156.745 md_002.py:3
33%
30.11.2025
creates a 256MB file in the current directory along with process for the job. This process reads complete file content in random order. Fio records the areas that have already been read and reads each area
33%
30.11.2025
53
47
44
439
128KB < < 256KB
0
2
0
0
0
0
0
2
256KB < < 512KB
2
2
2
3
2
