From: Ian Pilcher <arequipeno@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Small chunk size read performance penalty
Date: Sun, 18 Aug 2013 17:05:01 -0500 [thread overview]
Message-ID: <kurge6$qi0$1@ger.gmane.org> (raw)
Can anyone point me to a good explanation of the read performance impact
of small (RAID-5 and RAID-6) chunk sizes?
I understand why large chunks hurt write performance, but I haven't been
able to reason through the small-chunk/read case, and my Interweb
searches haven't really turned anything up.
The "read penalty" is definitely there; I can see it in the test data
from my NAS. I just don't understand *why* it's there.
Thanks!
--
========================================================================
Ian Pilcher arequipeno@gmail.com
Sometimes there's nothing left to do but crash and burn...or die trying.
========================================================================
next reply other threads:[~2013-08-18 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 22:05 Ian Pilcher [this message]
2013-08-18 22:16 ` Small chunk size read performance penalty Roberto Spadim
2013-08-19 1:40 ` Stan Hoeppner
2013-08-19 5:49 ` Ian Pilcher
2013-08-20 2:28 ` Stan Hoeppner
2013-08-19 3:01 ` Roberto Spadim
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='kurge6$qi0$1@ger.gmane.org' \
--to=arequipeno@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