From: Roman Mamedov <rm@romanrm.net>
To: Christer Solskogen <christer.solskogen@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Optimal chunk size for RAID5?
Date: Sun, 22 Feb 2015 17:30:47 +0500 [thread overview]
Message-ID: <20150222173047.1ea65d67@natsu> (raw)
In-Reply-To: <mccemd$8pi$1@ger.gmane.org>
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
--
With respect,
Roman
next prev parent reply other threads:[~2015-02-22 12:30 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 [this message]
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
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=20150222173047.1ea65d67@natsu \
--to=rm@romanrm.net \
--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).