From: Christer Solskogen <christer.solskogen@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: Optimal chunk size for RAID5?
Date: Mon, 23 Feb 2015 02:36:18 +0100 [thread overview]
Message-ID: <mce06j$i2h$1@ger.gmane.org> (raw)
In-Reply-To: <20150223085358.302830d1@notabene.brown>
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.
--
chs
next prev parent reply other threads:[~2015-02-23 1:36 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 [this message]
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='mce06j$i2h$1@ger.gmane.org' \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.