From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: "Conway S. Smith" <beolach@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: (was: Re: md: raid5 vs raid10 (f2,n2,o2) benchmarks [w/10 raptors])
Date: Thu, 3 Apr 2008 12:02:46 +0200 [thread overview]
Message-ID: <20080403100246.GA16459@rap.rap.dk> (raw)
In-Reply-To: <alpine.DEB.1.00.0804021349130.4140@p34.internal.lan>
On Wed, Apr 02, 2008 at 01:49:44PM -0400, Justin Piszcz wrote:
>
>
> On Wed, 2 Apr 2008, Justin Piszcz wrote:
>
> >
> >
> >On Wed, 2 Apr 2008, Conway S. Smith wrote:
I have referenced both of your benchmaks in the wiki on performance. So
now I just hope that your URLs will live forever. I also took down some
of your recomendations there.
I note that raid10,f2 has a much higher cpu load than raid10,n2 or
raid10,o2. How come? it is 31-38 % for f2, where n2 and o2 is around 15 %.
Also I note that the sequential read rate for o2 is nowhere near that of
n2, it is more like half of the n2 speed. I have seen claims from
normally trustworthy sources that o2 would obtain striping speeds.
IMHO theory would also say that o2 could not be striping.
And the optimized version from Justin impedes performance for f2, by
around 90 MB/s. How come?
best regards
keld
next prev parent reply other threads:[~2008-04-03 10:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 4:26 (was: Re: md: raid5 vs raid10 (f2,n2,o2) benchmarks [w/10 raptors]) Beolach
2008-04-02 12:16 ` Justin Piszcz
2008-04-02 14:02 ` Conway S. Smith
2008-04-02 17:44 ` Justin Piszcz
2008-04-02 17:49 ` Justin Piszcz
2008-04-03 10:02 ` Keld Jørn Simonsen [this message]
2008-04-03 10:26 ` Justin Piszcz
2008-06-25 18:48 ` Keld Jørn Simonsen
2008-06-25 19:09 ` David Lethe
2008-06-25 19:31 ` Justin Piszcz
2008-06-25 19:44 ` Keld Jørn Simonsen
2008-04-03 0:52 ` Dan 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=20080403100246.GA16459@rap.rap.dk \
--to=keld@dkuug.dk \
--cc=beolach@gmail.com \
--cc=jpiszcz@lucidpixels.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.