linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <roman@rm.pp.ru>
To: Jools Wills <jools@oxfordinspire.co.uk>
Cc: Konstantin Svist <fry.kun@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: messed up changing chunk size
Date: Mon, 19 Jul 2010 20:58:16 +0600	[thread overview]
Message-ID: <20100719205816.222ea76e@natsu> (raw)
In-Reply-To: <4C4451FC.30505@oxfordinspire.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]

On Mon, 19 Jul 2010 14:24:12 +0100
Jools Wills <jools@oxfordinspire.co.uk> wrote:

> >> I looked around and found that chunk size
> >> of 512 should work better.
> >
> > Not true, at least with RAID5/6 a chunk size of 64K performs faster, see
> > http://louwrentius.blogspot.com/2010/05/raid-level-and-chunk-size-benchmarks.html
> > http://alephnull.com/benchmarks/sata2009/chunksize.html
> 
> There is no mention in this benchmark tests if he modified the stripe 
> cache. With an increased stripe size a larger stripe cache would be 
> needed for good performance (at least from my experience)

That's true, but increasing the stripe cache helps across all chunk sizes, even
with relatively low 128K, see [1]. And I don't think that a large-chunk(512K)
configuration will significantly, if at all, outperform a small-chunks(64K)
one at any given stripe cache size (set to the same value in both cases).

There's also an opinion I heard from a couple of sources, that the stripe size
better be chosen so that either one stripe, or a whole stride fits inside the
CPU's L2 or L3 cache. Sounds logical, though I am not convinced that this is
what causes the performance difference between various stripe sizes.


[1]
http://peterkieser.com/2009/11/29/raid-mdraid-stripe_cache_size-vs-write-transfer/

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-07-19 14:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19  0:32 messed up changing chunk size Konstantin Svist
2010-07-19  0:41 ` Steven Haigh
2010-07-19  0:51   ` Konstantin Svist
2010-07-19  1:29 ` Guy Watkins
2010-07-19  1:45   ` Konstantin Svist
2010-07-19  1:51     ` Guy Watkins
2010-07-19  3:53 ` Roman Mamedov
2010-07-19 13:24   ` Jools Wills
2010-07-19 14:58     ` Roman Mamedov [this message]
2010-07-19 19:02   ` Keld Simonsen
2010-07-19 18:04 ` Konstantin Svist
2010-07-20  4:28   ` Konstantin Svist
2010-07-20  6:29     ` Konstantin Svist
2010-07-20 16:30       ` [SOLVED] " Konstantin Svist
2010-07-20 17:01         ` Konstantin Svist

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=20100719205816.222ea76e@natsu \
    --to=roman@rm.pp.ru \
    --cc=fry.kun@gmail.com \
    --cc=jools@oxfordinspire.co.uk \
    --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).