From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: "Keld Jørn Simonsen" <keld@dkuug.dk>
Cc: linux-raid@vger.kernel.org
Subject: Re: new bottleneck section in wiki
Date: Wed, 2 Jul 2008 12:43:40 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0807021241350.5166@p34.internal.lan> (raw)
In-Reply-To: <20080702155603.GA11156@rap.rap.dk>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1345 bytes --]
On Wed, 2 Jul 2008, Keld Jørn Simonsen wrote:
> The 66 MHz 64-bit PCI bus is capable of handling about 4 Gbit/s, or
> about 500 MB/s. This can also be a bottleneck with bigger arrays, eg a 6
> drive array will be able to deliver about 500 MB/s, and maybe you want
> also to feed a gigabyte ethernet card - 125 MB/s, totalling potentially
> 625 MB/s on the PCI bus.
>
> The PCI-Express bus v1.1 has a limit of 250 MB/s per lane per dirction,
> and that limit can easily be hit eg by a 4-drive array.
Correction, can easily be hit with two veliciraptors.
One veliciraptor for much of the read/write throughout the entire disk
is 120MiB/s and it slows down toward the middle obviously but FYI.
So two disks saturate it, I get 120MiB/s on a PCI-e x1 card but when I run two
disks on it at the same time (saturing them I only get 80-90MiB/s) on each of
them for an aggregate bandwidth of ~160MiB/s, it could be the card too.
03:00.0 RAID bus controller: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01)
04:00.0 RAID bus controller: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01)
05:00.0 RAID bus controller: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01)
(Not using RAID, they also act as a normal SATA controller)
Otherwise, very good write-up!
Justin.
next prev parent reply other threads:[~2008-07-02 16:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 15:56 new bottleneck section in wiki Keld Jørn Simonsen
2008-07-02 16:43 ` Justin Piszcz [this message]
2008-07-02 17:21 ` Keld Jørn Simonsen
2008-07-02 17:04 ` David Lethe
2008-07-02 17:51 ` Keld Jørn Simonsen
2008-07-02 18:08 ` David Lethe
2008-07-02 18:26 ` Keld Jørn Simonsen
2008-07-02 21:55 ` Roger Heflin
2008-07-02 19:45 ` Matt Garman
2008-07-02 20:05 ` Keld J?rn Simonsen
2008-07-02 20:24 ` Richard Scobie
2008-07-02 19:03 ` Matt Garman
2008-07-02 19:10 ` Jon Nelson
2008-07-02 19:35 ` Keld J?rn Simonsen
2008-07-02 19:38 ` Jon Nelson
2008-07-02 22:07 ` David Lethe
2008-07-03 12:28 ` Jon Nelson
2008-07-03 14:00 ` Justin Piszcz
2008-07-02 19:17 ` Robin Hill
2008-07-02 19:39 ` Keld J?rn Simonsen
2008-07-03 5:10 ` Doug Ledford
2008-07-02 21:45 ` Roger Heflin
2008-07-02 17:33 ` Iustin Pop
2008-07-02 18:14 ` 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=alpine.DEB.1.10.0807021241350.5166@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=keld@dkuug.dk \
--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).