- Thread Starter
- #26
That's one of the reasons I'm moving data off this server. It doesn't have enough SSD slots to allow for mirroring of the special device.
I found something else out. Two days ago I wrote a 10Gb test file and reading it was very fast: 500+MB/sec.
Re-reading the same file now, is quite slow:
but if I run it a second time, it's fast again
I assume some sort of cache goes into effect.
Pretty much any file I haven't accessed in a while only gets about 120MB/sec.
I tested with dd as well and got a bit slightly better speeds.
This has me wondering if maybe I've made a mistake somewhere in configuring this server ? Or I'm going crazy somehow. Veeam routinely reports writing at 300MB/sec. How can I really test what the hardware can do ?
I don't know what to believe anymore
I found something else out. Two days ago I wrote a 10Gb test file and reading it was very fast: 500+MB/sec.
Re-reading the same file now, is quite slow:
Code:
cat test1.img | pv -rtab > /dev/null
9.77GiB 0:01:06 [ 150MiB/s] [ 150MiB/s]
but if I run it a second time, it's fast again
Code:
cat test1.img | pv -rtab > /dev/null
9.77GiB 0:00:17 [ 566MiB/s] [ 566MiB/s]
I assume some sort of cache goes into effect.
Pretty much any file I haven't accessed in a while only gets about 120MB/sec.
I tested with dd as well and got a bit slightly better speeds.
This has me wondering if maybe I've made a mistake somewhere in configuring this server ? Or I'm going crazy somehow. Veeam routinely reports writing at 300MB/sec. How can I really test what the hardware can do ?
Code:
-rw-r--r-- 1 root pulsar 10485760000 May 13 23:18 test1.img
dd if=test1.img of=/dev/null bs=1M
10000+0 records in
10000+0 records out
10485760000 bytes transferred in 55.541516 secs (188791388 bytes/sec)
Code:
dd if=test1.img of=/dev/null bs=128k
80000+0 records in
80000+0 records out
10485760000 bytes transferred in 30.720653 secs (341326078 bytes/sec)
I don't know what to believe anymore