From: Adam Luter <luterac@bellsouth.net>
To: linux-raid@vger.kernel.org
Subject: Re: raid 1 vs raid 0+1
Date: Tue, 29 Oct 2002 09:39:30 -0600 [thread overview]
Message-ID: <20021029153930.GA21099@smeagol> (raw)
In-Reply-To: <1035904587.13219.304.camel@ralph.plexio.private>
On Tue, Oct 29, 2002 at 07:16:26AM -0800, Stephen Lee wrote:
> > real 0m5.024s
> >
>
> My systems are very different than what you describe above but here are
> some data points for reference. BTW, should that not be "of=$i/$j"?
>
> For a Dual P3/1.4Gig with 3x10000rpm SCSI drives running software raid5
> and ext3 on a 2.4.18 (Redhat 7.3 2.4.18-17.7) kernel:
>
> real 0m2.217s
>
> For a P3/1Gig with 2x10000rpm SCSI drive running software raid1 and ext3
> on a stock 2.4.18 kernel:
>
> real 0m3.349s
#!/bin/sh
time for i in {0,1,2,3,4,5,6,7,8,9}
do
mkdir $i
for j in {0,1,2,3,4,5,6,7,8,9}{0,1,2,3,4,5,6,7,8,9}
do
dd if=/dev/zero of=$i/$j bs=1k count=4 2>/dev/null
done
done
If everyone else is going to start squirting testosterone around, then
I'll add my share:
The above code, made an average time of about 3.7s . This is with
raid-5 (soft) 2.4.20pre8 with 4 IDE drives (Ibm 120 gig 7200rpm)
running at/on a Promise ATA/100 card (so 2 drives per bus). Also, the
filesystem is reiserfs, and running at medium-light load.
Changing the above code to:
#!/bin/sh
time for i in {0,1,2,3,4,5,6,7,8,9}{0,1,2,3,4,5,6,7,8,9}{0,1,2,3,4,5,6,7,8,9}
do
dd if=/dev/zero of=$i bs=1k count=4 2>/dev/null
done
(so that it writes them all to one directory), made the same time,
3.7s on average.
In fact, adding another 0..9 onto that loop only changed the average
time to 44 seconds.
For comparison the same tests on my system drive, a Maxtor IDE 40 gig
7200rpm drive connected to the onboard IDE controller (and also
reiserfs), resulted in 3.3 seconds, and 35 seconds respectively.
My conclusions are: IDE is damn fast and reiser kicks ass with small
files.
Of course alternate conclusions are that my raid-5 array suffers from
using two channels per drive (I know -- but when I put two promise
cards they or linux has DMA problems) and that I'm still behind the
pack when you throw 10krpm at me :) (2.2 seconds is nice!).
But, I'll never be rich enough for SCSI.
Back to the grind...
-Gryn (Adam Luter)
next prev parent reply other threads:[~2002-10-29 15:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 12:29 raid 1 vs raid 0+1 Antonello Piemonte
2002-10-29 13:14 ` Jakob Oestergaard
2002-10-29 15:16 ` Stephen Lee
2002-10-29 15:39 ` Adam Luter [this message]
2002-10-29 16:16 ` Stephen Lee
2002-10-29 21:08 ` Trent Piepho
2002-10-29 15:27 ` Antonello Piemonte
2002-10-29 15:42 ` Adam Luter
2002-10-29 16:19 ` Roy Sigurd Karlsbakk
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=20021029153930.GA21099@smeagol \
--to=luterac@bellsouth.net \
--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).