linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: linux-raid@vger.kernel.org
Subject: Re: What hardware for RAID5? (PCIe controller or fast onboard)
Date: Thu, 19 Mar 2009 08:10:58 +1100	[thread overview]
Message-ID: <49C16362.40006@eyal.emu.id.au> (raw)
In-Reply-To: <873adak6gt.fsf@frosties.localdomain>

A word of caution. 6 on-board SATA is not always enough. It is often the case
that using all will hit internal bandwidth limits. I find it common for 4 disks
to be handled OK but 5 are too much.

A simple test of 5 concurrent dd's will tell you if all disks are going full speed.
Some time one combination of 5 out of 6 (or 8) on-board sockets will perform better
than other and it is worth checking.

Eyal

Goswin von Brederlow wrote:
> Dexter Filmore <Dexter.Filmore@gmx.de> writes:
> 
>> I want to upgrade server hardware here, currently I have 5 Samsungs (sATA II) 
>> sitting on the onboard controller of an Asus K8N-E Socket754 board.
>> I guess the controller chips are both connected via PCI hence performance 
>> isn't really hot.
>>
>> Basically I need either a board with at least 6x sATA-II attached via PCIe or 
>> a "dumb" PCIe 4x or 8x controller card.
>>
>> Any recommendations?
>>
>> Dex
> 
> Anything that is not pci. PCIe or PCI-X will both be way
> faster. Server boards with 6x SATA-II onboard are hard to miss. And
> any cheap PCIe/PCI-X controler will probably do.
> 
> One important thing to think about is hotplug support. Do you need it
> or not?
> 
> Look for a board and then check out http://linux-ata.org/ for support.
> 
> MfG
>         Goswin

-- 
Eyal Lebedinsky	(eyal@eyal.emu.id.au)

  reply	other threads:[~2009-03-18 21:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 17:33 What hardware for RAID5? (PCIe controller or fast onboard) Dexter Filmore
2009-03-18 18:53 ` Goswin von Brederlow
2009-03-18 21:10   ` Eyal Lebedinsky [this message]
2009-03-20 13:28     ` Ryan Wagoner

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=49C16362.40006@eyal.emu.id.au \
    --to=eyal@eyal.emu.id.au \
    --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).