From: Tim Moore <linux-raid@nsr500.net>
To: linux-raid@vger.kernel.org
Cc: AndyLiebman@aol.com
Subject: Re: Maximum theoretical RAID-0 Speed
Date: Sun, 19 Dec 2004 10:43:00 -0800 [thread overview]
Message-ID: <41C5CBB4.1040606@nsr500.net> (raw)
In-Reply-To: <1c4.217b364e.2ef65ba7@aol.com>
AndyLiebman@aol.com wrote:
> I'm wondering if anyone on this list can shed some light on a question that
> pertains to the maximum theoretical read speed for the RAIDS on my Linux box,
> and whether I have reached it. My guess is, there are about 2 people in the
> world who possibly understand this. Linus Torvolds, perhaps. And maybe somebody
> else. But I'll give this list a try. I've met some pretty sharp people here.
Do some research on Garth Gibson at CMU's Parallel Computing group.
> Here's the scenario I have been testing.
>
> I have a single Xeon 3.06 processor set to use Hyperthreading, 2 GB of RAM on
> a SuperMicro Motherboard. The motherboard has 4 PCI "bus segments" with a
> total of six expansion slots. There are two PCI-X 133 Mhz slots (each associated
These are 64 bit slots, so 133MHz*64b/8bits/byte = 1.06GigaBytes/second
theoretical sustained
> with its own PCI bus segment). There is one PCI-X 100 Mhz slot (on ITS own
100*64/8 = 800MB/s sustained
> segment) and three PCI-32bit 33/66 Mhz slots (all sharing the same bus segment).
32*66/8 = 264MB/s shared
> Each of the PCI-X 133 Mhz slots also has one of the built-in GigE ports on it
GbE = 100MB/s
> (and I put all my other Intel GigE ports on these two bus segments --
> sometimes I have up to 6 ports in total on my machine). So I leave the 133 Mhz slots
> out of the RAIDS.
>
> I have 16 or 24 SATA drive bays in my enclosures.
>
> My basic design is to make Hardware RAID-5 arrays with 3ware 9000 cards and
64*66/8 = 528MB/s (RAID0), however I believe the 9000's drop to about
400MB/s on RAID5 (>4 ports), so that's your RAID5 bottleneck.
> Serial ATA drives. Then I make a Software RAID-0 stripe on top of the Hardware
> RAID-5. Sometimes I work with 8-channel 3ware cards, sometimes with 12-channel
> cards. So far, I have always put the cards (they're 66Mhz cards) in a
> combination of the 3 PCI 33/66 Mhz slots and the one PCI-X 100 Mhz slot.
So your max throughput assuming a max load on each PCI/66 slot is 88MB/s
each, the PCI/100 is 400MB/s (3ware limit). Put your 3ware cards on the
PCI/133 slots first, the the PCI/100, then the PCI/33.
> So, as I said above, that means I don't have any drives connected to the two
> PCI-X 133 slots (or to the segments they correspond to) because that would
> slow down the bus speed for those segments and presumably hurt my network
> performance.
Since the PCI/133 bandwidth available is about 1GB/s and a GbE port
consumes 100MB/s, that leaves 900MB/s for disk controllers that will only
do 400MB/s. On the 100MHz slot you get 800MB/s. This is the first thing
to change, then retest.
Cheers,
--
| for direct mail add "private_" in front of user name
next prev parent reply other threads:[~2004-12-19 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 4:20 Maximum theoretical RAID-0 Speed AndyLiebman
2004-12-19 4:54 ` Guy
2004-12-19 18:43 ` Tim Moore [this message]
2004-12-19 18:53 ` Tim Moore
2004-12-20 11:08 ` Holger Kiehl
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=41C5CBB4.1040606@nsr500.net \
--to=linux-raid@nsr500.net \
--cc=AndyLiebman@aol.com \
--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).