From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: "Keld Jørn Simonsen" <keld@dkuug.dk>, linux-raid@vger.kernel.org
Subject: Re: strange performance of raid0
Date: Sun, 15 Feb 2004 21:49:57 +0100 [thread overview]
Message-ID: <20040215204957.GA21117@rap.rap.dk> (raw)
In-Reply-To: <Pine.LNX.4.44.0402151523000.11668-100000@coffee.psychology.mcmaster.ca>
On Sun, Feb 15, 2004 at 03:35:32PM -0500, Mark Hahn wrote:
> > > The you don't get as good performance because hdc1 is slow enough to
> > > really drag it down.
>
> right.
>
> > I would have thought the disks would have worked towards gaining
> > performance enhancements in some cumulative way, is that not so, in theory?
>
> raid0 stripes IO across devices, so more devices help, in general.
> but suppose your config stores 1k per disk. a 3k write would
> touch all three disks. when would that write complete? according
> to your numbers, hdc1 takes much longer than the other two.
> that means that a large upper-level IO request (all three disks)
> will complete at about 3x16 MB/s (ignoring overhead, etc).
So max thruput in sequential read would never be faster than the slowest
disk times the total number of drives. Sounds right there, then
3 * 16 is 48, close to the observed value of 45.
> > > You probably can't get 100mb/s with the two because that would be pretty
> > > efficient, and there's probably more overhead than that.
>
> 100 MB/s is a pretty agressive goal for a duron: the speed of the CPU and
> memory bandwidth *DO* have a significant effect on how well raid0 scales,
> and where it tops out. hdparm -t is also quite cpu-inefficient, as
> benchmarks go.
Why should the duron CPU speed be a problem? Or the RAM?
> > > Shouldn't the 80gb drive be going faster than 16mb/s though? Have you
> > > checked hdparm to make sure dma and all the goodies are turned on for
> > > it?
>
> 16 MB/s is a clear config or measurement mistake. 16 MB/s is the speed of
> disks from 5+ years ago, and >= 80G didn't exist back then.
yeah, something is wrong there. I observed a going of about 40 MB/s
a couple of days ago on the same disk.
keld
next prev parent reply other threads:[~2004-02-15 20:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 10:04 strange performance of raid0 Keld Jørn Simonsen
2004-02-15 9:54 ` Matt Thrailkill
2004-02-15 12:05 ` Keld Jørn Simonsen
2004-02-15 11:55 ` Matt Thrailkill
2004-02-15 16:48 ` Keld Jørn Simonsen
2004-02-15 20:35 ` Mark Hahn
2004-02-15 20:49 ` Keld Jørn Simonsen [this message]
2004-02-15 23:58 ` Keld Jørn Simonsen
2004-02-17 17:50 ` Gregory Leblanc
2004-02-17 23:26 ` Keld Jørn Simonsen
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=20040215204957.GA21117@rap.rap.dk \
--to=keld@dkuug.dk \
--cc=hahn@physics.mcmaster.ca \
--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.