linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Christer Solskogen <christer.solskogen@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Optimal chunk size for RAID5?
Date: Mon, 23 Feb 2015 14:28:57 +1100	[thread overview]
Message-ID: <20150223142857.50206a19@notabene.brown> (raw)
In-Reply-To: <mce06j$i2h$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]

On Mon, 23 Feb 2015 02:36:18 +0100 Christer Solskogen
<christer.solskogen@gmail.com> wrote:

> On 22.02.2015 22:53, NeilBrown wrote:
> 
> > There is no "Optimal" without reference to a particular work load.  Or
> > particular hardware.
> >
> 
> Do you know of such a reference? I mean, some stats that show type of 
> workload / chunk size. The only one I've found is the 5 year old 
> benchmark that was done ( 
> http://louwrentius.com/linux-raid-level-and-chunk-size-the-benchmarks.html) 
> - which shows that under benchmarking with dd that 64 is preferred.
> 

Interesting graphs ... but when you see a big jump like they show between 64
and 128K chunk sizes for RAID5/6, that doesn't mean "64K is better" but
"something strange is happening here".  My guess is that read-ahead is
working very well for some reason.

If your actually workload is writing 10GB files with 'dd', then the graphs
might be useful.  For other workloads ... it's hard to tell.

Nothing beats performing your own tests on your own hardware with your own
choice of filesystem and getting your own results.

I did some tests myself recently (which I really want to automate and turn
into web pages etc ... one day).
For RAID5 on 4 drives I used chunk sizes of 4, 16, 64, 256, 1024 and applied
a variety of fio loads use XFS.

The only load that showed significant variation of chunk sizes was sequential
read which gets generally faster with larger chunk sizes, though for some
layouts (I tried la, ls, ra, rs) 1024k chunks were worse than 256k.

So any reference you find will probably lead you astray.

NeilBrown

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

      reply	other threads:[~2015-02-23  3:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-22 11:31 Optimal chunk size for RAID5? Christer Solskogen
2015-02-22 12:30 ` Roman Mamedov
2015-02-22 12:46   ` Christer Solskogen
2015-02-22 14:33   ` Alireza Haghdoost
2015-02-22 21:53     ` NeilBrown
2015-02-23  1:36       ` Christer Solskogen
2015-02-23  3:28         ` NeilBrown [this message]

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=20150223142857.50206a19@notabene.brown \
    --to=neilb@suse.de \
    --cc=christer.solskogen@gmail.com \
    --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).