From: Joe Williams <jwilliams315@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: increasing stripe_cache_size decreases RAID-6 read throughput
Date: Wed, 28 Apr 2010 13:40:56 -0700 [thread overview]
Message-ID: <m2t11f0870e1004281340v21421e55r2af9a813c0320b6b@mail.gmail.com> (raw)
In-Reply-To: <20100428072419.22779335@notabene.brown>
I did some tests, starting with the default values of 256 for
stripe_cache_size and 3072 for read_ahead_kb, and doubling them both
until performance stopped improving. Here are the best results that I
saw:
# echo 2048 > /sys/block/md0/md/stripe_cache_size
# echo 24576 > /sys/block/md0/queue/read_ahead_kb
# iozone -a -y64K -q16M -s4G -e -f iotest -i0 -i1 -i2
random random
KB reclen write rewrite read reread read write
4194304 64 241087 259892 243478 248102 7745 16161
4194304 128 259503 261886 244612 247157 13417 26812
4194304 256 260438 268077 240211 238916 21884 37527
4194304 512 243511 250004 252507 252276 34694 48868
4194304 1024 244744 253905 258920 250495 52351 76356
4194304 2048 240910 250500 253800 265361 79848 100131
4194304 4096 244283 253516 271940 272117 101737 137386
4194304 8192 239110 246370 262118 269687 103437 164715
4194304 16384 240698 249182 239378 253896 119437 198276
250 MB/s reads and writes is quite nice for a 5 drive RAID-6.
But I still do not understand why it is necessary to increase the
stripe_cache_size to 16 full stripes in order to optimize sequential
write speed.
next prev parent reply other threads:[~2010-04-28 20:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-24 23:36 increasing stripe_cache_size decreases RAID-6 read throughput Joe Williams
2010-04-24 23:45 ` Joe Williams
2010-04-27 6:41 ` Neil Brown
2010-04-27 17:18 ` Joe Williams
2010-04-27 21:24 ` Neil Brown
2010-04-28 20:40 ` Joe Williams [this message]
2010-04-29 4:34 ` Neil Brown
2010-05-04 0:06 ` Joe Williams
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=m2t11f0870e1004281340v21421e55r2af9a813c0320b6b@mail.gmail.com \
--to=jwilliams315@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).