From: Ming Zhang <mingz@ele.uri.edu>
To: Dan Christensen <jdc@uwo.ca>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID-5 streaming read performance
Date: Wed, 13 Jul 2005 08:24:54 -0400 [thread overview]
Message-ID: <1121257494.5504.4.camel@localhost.localdomain> (raw)
In-Reply-To: <87mzorfmdx.fsf@uwo.ca>
On Tue, 2005-07-12 at 22:52 -0400, Dan Christensen wrote:
> Ming Zhang <mingz@ele.uri.edu> writes:
>
> > On Mon, 2005-07-11 at 11:11 -0400, Dan Christensen wrote:
> >> I was wondering what I should expect in terms of streaming read
> >> performance when using (software) RAID-5 with four SATA drives. I
> >> thought I would get a noticeable improvement compared to reads from a
> >> single device, but that's not the case. I tested this by using dd to
> >> read 300MB directly from disk partitions /dev/sda7, etc, and also using
> >> dd to read 300MB directly from the raid device (/dev/md2 in this case).
> >> I get around 57MB/s from each of the disk partitions that make up the
> >> raid device, and about 58MB/s from the raid device. On the other
> >> hand, if I run parallel reads from the component partitions, I get
> >> 25 to 30MB/s each, so the bus can clearly achieve more than 100MB/s.
> >>
> >> [...]
> >>
> >> System:
> >> - Athlon 2500+
> >> - kernel 2.6.12.2 (also tried 2.6.11.11)
> >> - four SATA drives (3 160G, 1 200G); Samsung Spinpoint
> >> - SiI3114 controller (latency_timer=32 by default; tried 128 too)
> >
> > only 1 card? 4 port? try some other brand card and try to use several
> > cards at the same time. i met some poor cards before.
>
> Yes, one 4-port controller. It's on the motherboard.
>
> I thought that since I get good throughput doing parallel reads from
> the four drives (see above) that would eliminate the controller as the
> bottleneck. Am I wrong?
>
have u try the parallel write?
> Dan
> -
> 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:[~2005-07-13 12:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 15:11 RAID-5 streaming read performance Dan Christensen
2005-07-13 2:08 ` Ming Zhang
2005-07-13 2:52 ` Dan Christensen
2005-07-13 3:15 ` berk walker
2005-07-13 12:24 ` Ming Zhang [this message]
2005-07-13 12:48 ` Dan Christensen
2005-07-13 12:52 ` Ming Zhang
2005-07-13 14:23 ` Dan Christensen
2005-07-13 14:29 ` Ming Zhang
2005-07-13 17:56 ` Dan Christensen
2005-07-13 22:38 ` Neil Brown
2005-07-14 0:09 ` Ming Zhang
2005-07-14 1:16 ` Neil Brown
2005-07-14 1:25 ` Ming Zhang
2005-07-13 18:02 ` David Greaves
2005-07-13 18:14 ` Ming Zhang
2005-07-13 21:18 ` David Greaves
2005-07-13 21:44 ` Ming Zhang
2005-07-13 21:50 ` David Greaves
2005-07-13 21:55 ` Ming Zhang
2005-07-13 22:52 ` Neil Brown
2005-07-14 3:58 ` Dan Christensen
2005-07-14 4:13 ` Mark Hahn
2005-07-14 21:16 ` Dan Christensen
2005-07-14 21:30 ` Ming Zhang
2005-07-14 23:29 ` Mark Hahn
2005-07-15 1:23 ` Ming Zhang
2005-07-15 2:11 ` Dan Christensen
2005-07-15 12:28 ` Ming Zhang
2005-07-14 12:30 ` Ming Zhang
2005-07-14 14:23 ` Ming Zhang
2005-07-14 17:54 ` Dan Christensen
2005-07-14 18:00 ` Ming Zhang
2005-07-14 18:03 ` Dan Christensen
2005-07-14 18:10 ` Ming Zhang
2005-07-14 19:16 ` Dan Christensen
2005-07-14 20:13 ` Ming Zhang
2005-07-15 2:38 ` Dan Christensen
2005-07-15 6:01 ` Holger Kiehl
2005-07-15 12:29 ` Ming Zhang
2005-07-13 22:42 ` Neil Brown
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=1121257494.5504.4.camel@localhost.localdomain \
--to=mingz@ele.uri.edu \
--cc=jdc@uwo.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 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).