From: Simon McNair <simon@mcnair.co.uk>
To: Drew <drew.kay@gmail.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: single threaded parity calculation ?
Date: Sat, 16 Apr 2011 20:07:14 +0100 [thread overview]
Message-ID: <4DA9E8E2.20701@mcnair.co.uk> (raw)
In-Reply-To: <BANLkTims2gPKdxOo4_dd1NAnOz=CcL6yGQ@mail.gmail.com>
Drew,
Thanks for the response. Phil is already intimately familiar with this
but it's an Asus p7t deluxe v2 and the card is a pcie x4 supermicro 8
port AOC-SASLP-MV8.
Simon
On 16 Apr 2011, at 14:45, Drew <drew.kay@gmail.com
<mailto:drew.kay@gmail.com>> wrote:
>> iostat reports 83MB/s for each disk, running up to 830MB/s for all 10
>> disks,
>> but the max read speed of the array is approx 256MB/s.
>
> This may be a dumb question but what motherboard & disk controllers
> are you using and how are they setup?
>
> That 256MB/s feels to me like you may be bumping up against a
> bandwidth limitation of your bus. PCI (32bit/33MHz) is limited to
> 133MB/s max and PCIe(1.0/2.0) is limited to 250/500MB/s per lane. To
> sustain 830MB/s you need at least a PCIe (1.0) x4 or PCI-X 133
> controller card which are both rated for (theoretically) 1GB/s.
>
> As an aside, for read speeds on a RAID-5, the parity disk isn't used
> so theoretical maximum in this case is 9x83MB/s or 747MB/s. ;-)
>
>
> --
> Drew
>
> "Nothing in life is to be feared. It is only to be understood."
> --Marie Curie
prev parent reply other threads:[~2011-04-16 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 19:18 single threaded parity calculation ? Simon McNair
2011-04-15 20:54 ` Phil Turmel
2011-04-15 21:28 ` Phil Turmel
2011-04-15 21:44 ` Simon Mcnair
2011-04-15 21:46 ` NeilBrown
2011-04-16 13:45 ` Drew
2011-04-16 19:07 ` Simon McNair [this message]
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=4DA9E8E2.20701@mcnair.co.uk \
--to=simon@mcnair.co.uk \
--cc=drew.kay@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.