linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maurice Hilarius <maurice@harddata.com>
To: linux-raid@vger.kernel.org
Subject: Awful RAID5 random read performance
Date: Sat, 30 May 2009 15:46:32 -0600	[thread overview]
Message-ID: <4A21A938.6050907@harddata.com> (raw)

A friend writes:

On a recent machine set up with Raid5.
On a AMD Phenom II X4 810, and 4GB ram.
4 Seagate 7200.12  SATA 1TB drives,

I'm getting some rather impressive numbers for sequential read
(300MB/s+) and write (170MB/s+) but the random read is proving to be
absolutely atrocious.
iostat says its going at about 0.5MB/s,

I've seen plenty of references to people getting numbers in the double 
digits
for random reads on a md raid5 array, and one with slower disks to boot.

I tried disabling automatic acoustic management on the drives, but it 
didn't
seem to help at all.
 I really don't care that much about the noise coming from a file server 
stuck in a closet  ;)

Does anyone know why I'm seeing such bad random read times?
There's got to be some configuration error on my part, but I just can't
seem to find what it might be.

I've spent a few hours on google looking for various tweaks but
almost nobody even mentions random read/write times.
All everyone seems to care about is block sequential access time.
I'd be willing to sacrifice a fair portion of  my rather excellent 
sequential
times for much better random access.

-- 
Regards, Maurice

             reply	other threads:[~2009-05-30 21:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-30 21:46 Maurice Hilarius [this message]
2009-05-31  6:25 ` Awful RAID5 random read performance Michael Tokarev
2009-05-31  7:47   ` Thomas Fjellstrom
2009-05-31 12:29     ` John Robinson
2009-05-31 15:41       ` Leslie Rhorer
2009-05-31 16:56         ` Thomas Fjellstrom
2009-05-31 18:26           ` Keld Jørn Simonsen
2009-06-02 18:54           ` Bill Davidsen
2009-06-02 19:47             ` Keld Jørn Simonsen
2009-06-02 23:13               ` John Robinson
2009-06-03 18:38                 ` Bill Davidsen
2009-06-03 19:57                   ` John Robinson
2009-06-03 22:21                     ` Goswin von Brederlow
2009-06-04 11:23                       ` Keld Jørn Simonsen
2009-06-04 22:40                       ` Nifty Fedora Mitch
2009-06-06 23:06                       ` Bill Davidsen
2009-06-01  1:19         ` Carlos Carvalho
2009-06-01  4:57           ` Leslie Rhorer
2009-06-01  5:39             ` Thomas Fjellstrom
2009-06-01 12:43               ` Maurice Hilarius
2009-06-02 14:57                 ` Wil Reichert
2009-06-02 15:14                   ` Maurice Hilarius
2009-06-02 19:47               ` Bill Davidsen
2009-06-01 11:41             ` Goswin von Brederlow
2009-06-03  1:57               ` Leslie Rhorer
2009-05-31 17:19       ` Goswin von Brederlow
2009-06-01 12:01         ` John Robinson

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=4A21A938.6050907@harddata.com \
    --to=maurice@harddata.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 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).