From: Spelic <spelic@shiftmail.org>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: raid10 speed drops significantly on large chunks
Date: Wed, 24 Nov 2010 01:22:49 +0100 [thread overview]
Message-ID: <4CEC5AD9.4030708@shiftmail.org> (raw)
Hi there
I'm doing some testing on raid10 layouts and chunksizes.
I am checking chunksizes 128, 1024 and 8192, on a 6-disk array.
On streaming read / streaming write (dd bs=1M from/to /dev/zero
/dev/null) the speed of 128 and 1024 on my hardware is around 270MB/sec
writes (all layouts) and 280MB/sec(near)--450MB/sec(far) read speed.
But when I try chunksize 8192 speed drops significantly and I have
231(near)--175(far) write speed and 205(near)--323(far) read speed.
I tried the kitchen sink on settings... but there's no way to bring 8192
speed up to the others. I tried raising nr_requests on all the drives up
by a factor 16, changing schedulers, raising deadline scheduler
expirations, readahead on drives... no way.
This surprises me... what could be the reason? In particular on a near
layout I can't see what could be wrong with a big chunksize.
I suspect the situation would have gone worse if I went further up with
the chunksize.
There is plenty of free RAM (8GB free).
Thanks for your insights
reply other threads:[~2010-11-24 0:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CEC5AD9.4030708@shiftmail.org \
--to=spelic@shiftmail.org \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).