On 12/06/2014 11:30 PM, Eric Wheeler wrote:
On Sat, 6 Dec 2014, Jens Axboe wrote:
On 12/06/2014 03:40 PM, Eric Wheeler wrote:
On Fri, 5 Dec 2014, Mike Snitzer wrote:
I do wonder what the performance impact is on this for dm. Have you
tried a (worst case) test of writing blocks that are zero filled, but
with the last byte not being a zero?
The additional overhead of worst-case should be (nearly) equal to the
simplest test case of dd if=/dev/zero of=/dev/thinp/vol. In my testing
that was 1.4GB/s within KVM on an Intel Xeon(R) CPU E3-1230 V2 @
3.30GHz.
That seems way too slow for checking if it's zero or not... Memory
bandwidth should be way higher than that. The line above, was that
what you ran? How does it look with bs=4k or higher?
In userspace I can get ~12GB/s, so I think the algorithm is sound.
dd might not be the right tool for this.
It's straight forward looping through the vectors, it can't really work
any other way. But we need to figure out why it's so slow...
read : io=12233MB, bw=1432.7MB/s, iops=22922, runt= 8539msec
Can you suggest the right fio commandline to test sequential writes if
all zeros? I tried --zero_buffers but couldn't get it to write zeros,
writes kept going to disk.
zero_buffers=1
scramble_buffers=0
should get you all zeroes.
--
Jens Axboe
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
