public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Kropelin <akropel1@rochester.rr.com>
To: jw schultz <jw@pegasys.ws>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: raid0 slower than devices it is assembled of?
Date: Tue, 16 Dec 2003 16:11:31 -0500	[thread overview]
Message-ID: <20031216161131.A6197@mail.kroptech.com> (raw)
In-Reply-To: <20031216040156.GJ12726@pegasys.ws>; from jw@pegasys.ws on Mon, Dec 15, 2003 at 08:01:56PM -0800

On Mon, Dec 15, 2003 at 08:01:56PM -0800, jw schultz wrote:
> On Mon, Dec 15, 2003 at 02:34:54PM +0100, Witold Krecicki wrote:
> > Those are results of hdparm -tT on drives:
> > <cite>
> > /dev/md/1:
> >  Timing buffer-cache reads:   128 MB in  0.40 seconds =323.28 MB/sec
> >  Timing buffered disk reads:  64 MB in  1.75 seconds = 36.47 MB/sec
> > /dev/sda:
> >  Timing buffer-cache reads:   128 MB in  0.41 seconds =309.23 MB/sec
> >  Timing buffered disk reads:  64 MB in  1.46 seconds = 43.87 MB/sec
> > /dev/sdb:
> >  Timing buffer-cache reads:   128 MB in  0.41 seconds =315.32 MB/sec
> >  Timing buffered disk reads:  64 MB in  1.23 seconds = 52.04 MB/sec
> > </cite>
> 
> No Linux [R]AID improves sequential performance.  How would
> reading 65KB from two disks in alternation be faster than
> reading continuously from one disk?

Never say never:

/dev/sda:
 Timing buffer-cache reads:   128 MB in  3.34 seconds = 38.38 MB/sec
 Timing buffered disk reads:  64 MB in  8.60 seconds =  7.44 MB/sec
/dev/sdb:
 Timing buffer-cache reads:   128 MB in  3.40 seconds = 37.64 MB/sec
 Timing buffered disk reads:  64 MB in  8.60 seconds =  7.44 MB/sec

<...plus four more just like them...>

/dev/md0:
 Timing buffer-cache reads:   128 MB in  3.35 seconds = 38.17 MB/sec
 Timing buffered disk reads:  64 MB in  4.05 seconds = 15.79 MB/sec

md0 is a simple RAID0 of all six disks.

Yes, these disks are dirt slow to begin with (Andrew Morton once
mentioned he had pencils that wrote faster than my disks) but apparently
md manages to get some parallelism going, even for sequential reads.

(This is 2.6.0-test11-bk8, FWIW.)

--Adam


  parent reply	other threads:[~2003-12-16 21:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-15 13:34 raid0 slower than devices it is assembled of? Witold Krecicki
2003-12-15 15:44 ` Witold Krecicki
2003-12-16  4:01 ` jw schultz
2003-12-16 14:51   ` Helge Hafting
2003-12-16 16:42     ` Linus Torvalds
2003-12-16 20:58       ` Mike Fedyk
2003-12-16 21:11         ` Linus Torvalds
2003-12-17 10:53           ` Jörn Engel
2003-12-17 11:39           ` Peter Zaitsev
2003-12-17 16:01             ` Linus Torvalds
2003-12-17 18:37               ` Mike Fedyk
2003-12-17 21:55               ` bill davidsen
2003-12-17 17:02             ` bill davidsen
2003-12-17 20:14               ` Peter Zaitsev
2003-12-17 19:22       ` Jamie Lokier
2003-12-17 19:40         ` Linus Torvalds
2003-12-17 22:36           ` bill davidsen
2003-12-18  2:47         ` jw schultz
2003-12-17 22:29       ` bill davidsen
2003-12-18  2:18         ` jw schultz
2004-01-08  4:54       ` Greg Stark
2003-12-16 20:51     ` Andre Hedrick
2003-12-16 21:04       ` Andre Hedrick
2003-12-16 21:46         ` Witold Krecicki
2003-12-16 20:09   ` Witold Krecicki
2003-12-16 21:11   ` Adam Kropelin [this message]
2003-12-16 21:25 ` jw schultz

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=20031216161131.A6197@mail.kroptech.com \
    --to=akropel1@rochester.rr.com \
    --cc=jw@pegasys.ws \
    --cc=linux-kernel@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