From: Tiago Freire <tiago.freire@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: RAID performance / tuning?
Date: Thu, 2 Apr 2009 16:36:28 -0300 [thread overview]
Message-ID: <159a870e0904021236m6ef4444eh66ec42e34aa24291@mail.gmail.com> (raw)
In-Reply-To: <6c62e9d84a16902aebba9438b4e299d9.squirrel@localhost>
I would like to believe this is not the case with Intel ICH9R...
Anyway, I want to make sure I have done everything possible to speed
up my 6-disk RAID.
Scheduling concurernt IO may not have a best single solution, I know,
but is the kernel 'perfect' in the sense of giving the RAID / SATA
subsystems all the cpu cycles it needs to perform best (with the
lowest possible latency)? Or do we have some knobs to tune the kernel?
On Thu, Apr 2, 2009 at 2:41 PM, <david.hagood@gmail.com> wrote:
>
>> Why is it that software RAID on current systems still gets less
>> performance than hardware counterparts?
>
> Part of it can be crappy disk interfaces: I was running software raid with
> 2 SATA-SIL cards, and would frequently be disk-bound with the CPU still
> largely idle.
>
> The cards were incapable of talking to more than one drive at a time. They
> didn't support command queuing on the drives.
>
> As a result, the system would set up a stripe, queue up the writes, then
> have to wait as each write for EACH DISK in the 7 disk array was carried
> out.
>
> On a good hardware RAID controller, the disks can be written in parallel,
> and the controller will support command queuing - so disk writes can be
> run in parallel, and the writes themselves can be better optimized by the
> disks.
>
>
>
--
-----
Tiago Mikhael Pastorello Freire a.k.a. Brazilian Joe
prev parent reply other threads:[~2009-04-02 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 14:02 Tiago Freire
2009-04-02 17:41 ` david.hagood
2009-04-02 19:36 ` Tiago Freire [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=159a870e0904021236m6ef4444eh66ec42e34aa24291@mail.gmail.com \
--to=tiago.freire@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®