linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Scobie <richard@sauce.co.nz>
To: linux-raid@vger.kernel.org
Subject: Re: slow raid5 performance
Date: Tue, 23 Oct 2007 08:23:09 +1300	[thread overview]
Message-ID: <471CF89D.6020104@sauce.co.nz> (raw)
In-Reply-To: <352991.69437.qm@web52803.mail.re2.yahoo.com>

Peter wrote:
> Thanks Justin, good to hear about some real world experience. 

Hi Peter,

I recently built a 3 drive RAID5 using the onboard SATA controllers on 
an MCP55 based board and get around 115MB/s write and 141MB/s read.

A fourth drive was added some time later and after growing the array and 
filesystem (XFS), saw 160MB/s write and 178MB/s read, with the array 60% 
full.

Regards,

Richard

  reply	other threads:[~2007-10-22 19:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 17:21 slow raid5 performance Peter
2007-10-22 19:23 ` Richard Scobie [this message]
2007-10-22 19:33   ` Justin Piszcz
2007-10-22 20:18     ` Peter Grandi
  -- strict thread matches above, loose matches on Subject: below --
2007-10-22 17:18 Peter
2007-10-22 20:52 ` Peter Grandi
2007-10-22 16:15 Peter
2007-10-22 16:58 ` Justin Piszcz
2007-10-18 22:21 nefilim
2007-10-20 12:38 ` Peter Grandi

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=471CF89D.6020104@sauce.co.nz \
    --to=richard@sauce.co.nz \
    --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).