public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Matt M. Valites" <mval@axium.net>
To: linux-kernel@vger.kernel.org
Subject: Poor  I/O Performance with MegaRaid SATA 150-4; bug or feature?
Date: Sat, 16 Apr 2005 13:34:39 -0400	[thread overview]
Message-ID: <42614CAF.50606@axium.net> (raw)

Hail List,

I've been banging my head against this for a few days, and I wanted to
see if anyone here could lend a hand.

I have the following configuration:
P4 3.x Ghz
2GB Ram;
2 x 36GB WD Raptors; in a RAID1 (sda)
2 x 74GB WD Raptor (those 10K RPM SATA drives) in a RAID1(sdb)
Two free PCI-X slots, one of which occupied by a LSI MegaRaid SATA 150-4.

The problem is I/O on either one of these RAID devices seems to
be less than half what I'm expecting.   The file system used in my testing is
XFS, and I'm running kernel 2.6.11.6.

The test I'm doing is a simple:
# time dd if=/dev/zero of=./crap.file bs=1024 count=209715
Which results in a runtime of about ~53s, in the best case, with all the
scary write cache enabled.    I've tried with deadline, and
anticipatory.  I've also tried several kernels, namely a recent 2.4, so
I could test megaraid and megaraid2, similar results.

On my desktop box, with one of these drives connected via SATA, i get
~25s, also XFS.  (2.6.11-gentoo-r6 x86_64).

Is this an expected result?  I'm seeing much higher numbers posted around the
'Net.  Most of those results are from Windows boxes.

I've uploaded my kernel config, lspci -v, and two opreports of a bonnie++ run
to: http://www.muixa.com/lkml/

Any thoughts would be appreciated.
Thanks,
--
Matt M. Valites









             reply	other threads:[~2005-04-16 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-16 17:34 Matt M. Valites [this message]
2005-04-16 22:57 ` Poor I/O Performance with MegaRaid SATA 150-4; bug or feature? Andre Tomt
2005-04-17 15:53   ` Matt M. Valites

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=42614CAF.50606@axium.net \
    --to=mval@axium.net \
    --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