From: Raz <raziebe@gmail.com>
To: jnelson-linux-raid@jamponi.net
Cc: linux-raid@vger.kernel.org
Subject: Re: stripe_cache_size and performance
Date: Fri, 22 Jun 2007 18:01:59 +0300 [thread overview]
Message-ID: <5d96567b0706220801v76c1c19cl7448050e62e0860b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706211808140.5806@gheavc.wnzcbav.cig>
On 6/22/07, Jon Nelson <jnelson-linux-raid@jamponi.net> wrote:
> On Thu, 21 Jun 2007, Raz wrote:
>
> > What is your raid configuration ?
> > Please note that the stripe_cache_size is acting as a bottle neck in some
> > cases.
>
> Well, it's 3x SATA drives in raid5. 320G drives each, and I'm using a
> 314G partition from each disk (the rest of the space is quiescent).
what is the chunk size ?. Please note that a raid performance is dependent
on the access pattern to the disks. What is this raid aimed to do ?
more reads ? more writes ? If you can control the access pattern ,
you might be able to increase performance.
> > On 6/21/07, Jon Nelson <jnelson-linux-raid@jamponi.net> wrote:
> > >
> > > I've been futzing with stripe_cache_size on a 3x component raid5,
> > > using 2.6.18.8-0.3-default on x86_64 (openSUSE 10.2).
> > >
> > > With the value set at 4096 I get pretty great write numbers.
> > > 2048 and on down the write numbers slowly drop.
> > >
> > > However, at values above 512 the 'check' performance is terrible. By
> > > 'check' performance I mean the value displayed by /proc/mdstat after
> > > I issue:
> > >
> > > echo check > /sys/block/md0/md/sync_action
> > >
> > > When I say "terrible" I mean < 3MB/s.
> > > When I use 384, the performance goes to ~70MB/s
> > > 512.. 72-73MB/s
> > > 640.. 73-74MB/s
> > >
> > > 768.. 3300 K/s. Wow!
> > >
> > > Can somebody 'splain to me what is going on?
> > >
> > > --
> > > Jon Nelson <jnelson-linux-raid@jamponi.net>
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > >
> >
> >
> > --
> > Raz
> >
> >
> >
>
> --
> Jon Nelson <jnelson-linux-raid@jamponi.net>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Raz
next prev parent reply other threads:[~2007-06-22 15:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 18:28 stripe_cache_size and performance Jon Nelson
2007-06-21 19:42 ` Raz
2007-06-21 23:09 ` Jon Nelson
2007-06-22 15:01 ` Raz [this message]
2007-06-22 15:10 ` Justin Piszcz
2007-06-25 16:48 ` Bill Davidsen
2007-06-25 17:00 ` Justin Piszcz
2007-06-25 18:20 ` Justin Piszcz
2007-06-25 18:21 ` Justin Piszcz
2007-06-25 18:42 ` Justin Piszcz
2007-06-25 19:48 ` stripe_cache_size and performance [BUG with =64kb] Justin Piszcz
2007-06-25 19:49 ` Justin Piszcz
2007-06-25 20:36 ` Justin Piszcz
2007-06-25 20:42 ` Justin Piszcz
2007-06-25 22:12 ` stripe_cache_size and performance Jon Nelson
2007-06-25 22:19 ` Dan Williams
2007-06-25 23:23 ` Jon Nelson
2007-06-25 22:21 ` Justin Piszcz
2007-06-26 13:58 ` Jon Nelson
2007-06-26 14:00 ` Justin Piszcz
2007-06-26 14:16 ` Jon Nelson
2007-06-26 14:37 ` Justin Piszcz
2007-06-26 15:22 ` Jon Nelson
2007-06-26 15:54 ` Justin Piszcz
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=5d96567b0706220801v76c1c19cl7448050e62e0860b@mail.gmail.com \
--to=raziebe@gmail.com \
--cc=jnelson-linux-raid@jamponi.net \
--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).