From: NeilBrown <neilb@suse.de>
To: Alireza Haghdoost <alireza@cs.umn.edu>
Cc: Roman Mamedov <rm@romanrm.net>,
Christer Solskogen <christer.solskogen@gmail.com>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Optimal chunk size for RAID5?
Date: Mon, 23 Feb 2015 08:53:58 +1100 [thread overview]
Message-ID: <20150223085358.302830d1@notabene.brown> (raw)
In-Reply-To: <CAB-428=7y-KSbCeXo6y6o5Jfzgf-5h6pfYxY+4Z74bqYp=oMUg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
On Sun, 22 Feb 2015 08:33:02 -0600 Alireza Haghdoost <alireza@cs.umn.edu>
wrote:
> On Sun, Feb 22, 2015 at 6:30 AM, Roman Mamedov <rm@romanrm.net> wrote:
> > On Sun, 22 Feb 2015 12:31:23 +0100
> > Christer Solskogen <christer.solskogen@gmail.com> wrote:
> >
> >> There are so many different views on the internet
> >
> > ...and yet you're asking for some more? :)
> >
> >> Is there even such a thing as optimal chunk size?
> >
> > 64K should be fine:
> > http://louwrentius.com/linux-raid-level-and-chunk-size-the-benchmarks.html
> >
>
> I have seen that people report 64K chunk size results better
> performance. However, I was not able to find why mdadm maintainers
> decided to switch into 512K default chunk size a few years ago ? Was
> that decision related to the write-intent bitmap overhead ?
No, write-intent-bitmap sizing is completely independent from chunk sizes.
I don't remember the detail for the change, but some measurement must have
gone faster with larger chunk size.
single threaded loads tend to prefer large chunk sizes.
multi-threaded small-request random IO tends to prefer smaller chunk sizes.
There is no "Optimal" without reference to a particular work load. Or
particular hardware.
NeilBrown
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2015-02-22 21:53 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 [this message]
2015-02-23 1:36 ` Christer Solskogen
2015-02-23 3:28 ` NeilBrown
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=20150223085358.302830d1@notabene.brown \
--to=neilb@suse.de \
--cc=alireza@cs.umn.edu \
--cc=christer.solskogen@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=rm@romanrm.net \
/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).