51%
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
51%
13.12.2018
disk reads: 1306 MB in 3.00 seconds = 434.77 MB/sec
federico@cybertron:~$ sudo hdparm -W /dev/sdb
/dev/sdb:
write-caching = 1 (on)
federico@cybertron:~$ sudo hdparm -W 0 /dev/sdb
/dev/sdb:
write
50%
15.02.2012
2
0
0
0
0
0
2
256KB < < 512KB
2
2
2
3
2
2
2
3
512KB < < 1MB
3
2
2
50%
26.01.2012
2
0
0
0
0
0
2
256KB < < 512KB
2
2
2
3
2
2
2
3
512KB < < 1MB
3
2
2
50%
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
50%
27.08.2014
record size, (2) sequential read testing with 1MB record size, and (3) random write and read (4KB). In running these tests, I wanted to see what block layer information ioprof revealed.
The system I
50%
22.05.2012
/group_gz | 212 kB 00:00
Package flex-2.5.35-8.el6.x86_64 already installed and latest version
Package gcc-4.4.6-3.el6.x86_64 already installed and latest version
Package autoconf-2.63-5.1.el6.noarch
50%
30.01.2020
=test
test: (g=0): rw=randwrite, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=32
fio-3.12
Starting 1 process
Jobs: 1 (f=1): [w(1)][100.0%][w=654MiB/s][w=167k IOPS][eta 00m:00s
49%
11.04.2016
on disk; 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
49%
19.11.2019
, ioengine=libaio, iodepth=32
fio-3.1
Starting 1 process
Jobs: 1 (f=1): [w(1)][100.0%][r=0KiB/s,w=1401KiB/s][r=0,w=350 IOPS][eta 00m:00s]
test: (groupid=0, jobs=1): err= 0: pid=3104: Sat Oct 12 14:39:08 2019
write: IOPS=352
