linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: thomas62186218@aol.com
Cc: rabbit+list@rabbit.us, linux-raid@vger.kernel.org
Subject: Re: Raid6 write performance
Date: Mon, 19 Jan 2009 13:48:37 +0100	[thread overview]
Message-ID: <20090119124837.GC23623@rap.rap.dk> (raw)
In-Reply-To: <8CB482475EFC01A-17F0-256E@webmail-dx12.sysops.aol.com>

On Mon, Jan 19, 2009 at 03:10:01AM -0500, thomas62186218@aol.com wrote:
> 
> I tested RAID 5 and RAID 6 with 12 x 15K SAS drives on Ubuntu 8.04 
> 64-bit and found their performance to be about the same. I used 256 K 
> chunk size, v1.0 superblocks, stripecachesize of 16384, and readahead 
> of 65536.
> 
> RAID 5 reads: 774 MB/sec
> RAID 5 writes: 585 MB/sec
> 
> RAID 6 reads: 742 MB/sec
> RAID 6 writes: 559 MB/sec
> 
> My CPU utilization remains under 10% though during writes, and I'm 
> wondering what can be done to get write performance closer to read 
> performance. I have dual quad-core CPUs so there's plenty of CPU to go 
> around. Any ideas on that front?

Seems like it is the same equipment that you also did the raid10,f2
tests for. I think it would be interesting to have a consolidated list
of performance comparisons, when you have completed your tweakings.
Is that part of your plan?

best regards
keld

  parent reply	other threads:[~2009-01-19 12:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-19  7:40 Raid6 write performance Peter Rabbitson
2009-01-19  8:10 ` thomas62186218
2009-01-19  9:07   ` NiftyFedora Mitch
2009-01-26 18:47     ` Bill Davidsen
2009-01-19 12:48   ` Keld Jørn Simonsen [this message]
2009-01-19 12:50     ` Peter Rabbitson
2009-01-19 10:37 ` Peter Rabbitson
2009-01-19 10:58   ` Bernd Schubert
2009-01-19 11:01     ` Peter Rabbitson
2009-01-19 11:08       ` Bernd Schubert
2009-02-28  1:04 ` H. Peter Anvin
2009-03-01 19:12   ` Michał Przyłuski
2009-03-01 20:35     ` H. Peter Anvin
2009-03-01 19:19   ` Peter Rabbitson
2009-03-13 17:11     ` Bill Davidsen

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=20090119124837.GC23623@rap.rap.dk \
    --to=keld@dkuug.dk \
    --cc=linux-raid@vger.kernel.org \
    --cc=rabbit+list@rabbit.us \
    --cc=thomas62186218@aol.com \
    /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).