From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: Matt Thrailkill <xwred1@modestolan.com>
Cc: "Keld Jørn Simonsen" <keld@dkuug.dk>, linux-raid@vger.kernel.org
Subject: Re: strange performance of raid0
Date: Sun, 15 Feb 2004 13:05:25 +0100 [thread overview]
Message-ID: <20040215120525.GA19434@rap.rap.dk> (raw)
In-Reply-To: <1076838850.28006.6.camel@stoneburner.xwredwing.net>
On Sun, Feb 15, 2004 at 01:54:11AM -0800, Matt Thrailkill wrote:
> The you don't get as good performance because hdc1 is slow enough to
> really drag it down. Think about it, if reads are all going about
> sequentially, it has to spend alot of time waiting on that 16mb/s drive
> compared to the others.
I would have thought the disks would have worked towards gaining
performance enhancements in some cumulative way, is that not so, in theory?
So why is 3 disks slower than 2?
> You probably can't get 100mb/s with the two because that would be pretty
> efficient, and there's probably more overhead than that.
>
> 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?
I have a 40 GB segate disk also, on the same motherboard IDE
controller, it runs about 40 MB/s. So yes, the hdc1
should go faster, and I have measured something like 40 MB/s
on it in idler times. I think it is because it is running other
processes. The machine is a ftp mirror and the disk has RedHat
and Fedora ISO images, so it is quite popular.
> On Sun, 2004-02-15 at 02:04, Keld Jørn Simonsen wrote:
> > Hi
> >
> > I have some strange performance results on a raid0
> > I have 4 IDE disks on two controllers, the one on the
> > motherboard of the duron 1 GHz mackine, the other a promise TX2 plus
> > SATA + PATA controller. I run kernel 2.4.22
> >
> > The disks and hdparm -t on each of them
> >
> > /dev/hdc1 seagate 80 GB 16 MB/s
> > /dev/sda1 maxtor sata 200 GB 50 MB/s
> > /dev/sdb7 maxtor 160 GB 54 MB/s
> >
> > The partitions are al about 5 GB each.
> >
> > If I make a raid0 device of all of them I get a thruput of 45 MB/s
> > IIf I exclude the hdc1 partition, I get around 75 MB/s.
> > The system is a little loaded - but that would be normal operating
> > conditions. CPU is 90 % idle. I have about 100 MB free RAM.
> >
> > Why is it slower with 3 disks in the raid0 than
> > 2 disks? Why don't I get approx 100 MB/s out of just the two?
> >
> > Best regards
> > Keld
-
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
next prev parent reply other threads:[~2004-02-15 12:05 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 [this message]
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
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=20040215120525.GA19434@rap.rap.dk \
--to=keld@dkuug.dk \
--cc=linux-raid@vger.kernel.org \
--cc=xwred1@modestolan.com \
/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).