On 10/07/2014 12:44 PM, P. Gautschi wrote:
I've created a RAID5 on 5 identical SATA disks. Doing some performance
measurements
with dd I get a disappointing performance.
A dd with bs=1M on a btrfs created on md0 transfers about 110 MB/s.
(both read and write)
A dd on md0 has the same write speed but only about 20 MB/s on read.
In all of the tests I hear the disk constantly seeking. This was also
the case
during creation of the array.
I also created a RAID4 to make sure that I doesn't get fooled by the
stripe layout of RAID5.
Now I get about 110 MB/s for write and 230 MB/s for read on md0. But
the constant
seeking is still present for both read and write and during creation
of the array.
Why are the disk perform so many seek operations? I think a sequential
access on md0 should
cause a sequential access on the individual disk.
Hi P. Gautschi
How can you find the seek operations? Do you use blktrace or other
commands? Can you give the
detail commands and informations?
BTW, I think ever if you use larger chunksize when create raid,
there is few RMW. There is a period to wait for full write.
I have to add that I did something unusual: I created the RAID4/5 with
a chunk size of 4KiB.
The idea of this was that when I'm going to use btrfs with the default
nodesize of 16KiB
all node write will fill a full stripe and there won't be any RMW at
all. (both fortunate
for performance and integrity in a power loss situation.)
Nevertheless I think a sequential access on the array should cause a
sequential access on the
disks for any chunk size if the read/write block size is a exact
multiple of
the (numdisks-1)*chunk size.
Is there any explanation for the seeks and how do I get rid of them?
Patrick
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
