From: Bill Davidsen <davidsen@tmr.com>
To: NiftyFedora Mitch <niftyfedora@niftyegg.com>
Cc: thomas62186218@aol.com, rabbit+list@rabbit.us,
linux-raid@vger.kernel.org
Subject: Re: Raid6 write performance
Date: Mon, 26 Jan 2009 13:47:05 -0500 [thread overview]
Message-ID: <497E0529.3050501@tmr.com> (raw)
In-Reply-To: <1cd4f41f0901190107l53d02785l844da71a6643605@mail.gmail.com>
NiftyFedora Mitch wrote:
> On Mon, Jan 19, 2009 at 12:10 AM, <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?
>>
>> -Thomas
>>
>>
>> -----Original Message-----
>> From: Peter Rabbitson <rabbit+list@rabbit.us>
>> To: linux-raid@vger.kernel.org
>> Sent: Sun, 18 Jan 2009 11:40 pm
>> Subject: Raid6 write performance
>>
>
>
>> Hi,
>>
>> I am experimenting with raid6 on 4 drives on 2.6.27.11. The problem I am
>> having is that no matter what chunk size I use, the write benchmark
>> always comes out at single drive speed, although I should be seeing
>> double drive speed (read speed is at near 4x as expected). Is there some
>> hidden setting that I am overlooking, or is this a current known
>> limitation of raid6? In contrast if I make a raid5 on these 4 drives, I
>> get the expected 3xdrive write speed, and occasionally 4xdrive linear
>> read speed.
>>
>> When the write test is running, I get about 14% of system cpu a sporadic
>> 40% of iowait and the rest idle at all times (machine is in runlevel 1
>> so not to screw with results). Anyone has any ideas?
>>
>
> Read bandwidth will always be quicker than writes with parity.
> Data and parity both need to be written in an atomic way so the completion
> will be gated by the last write to be "posted as done" back to the
> system.
>
> It can pay to locate the journal on a physically different, smaller
> and faster resource.
> One informative experiment might be to mount the file system as ext2 and compare
> and contrast with the same FS mounted as ext3. I am not recommending ext2
> over ext3 other than as an experiment to see what the impact of the
> journal activity is...
>
>
Also see noatime, relatime, etc.
--
Bill Davidsen <davidsen@tmr.com>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
next prev parent reply other threads:[~2009-01-26 18:47 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 [this message]
2009-01-19 12:48 ` Keld Jørn Simonsen
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=497E0529.3050501@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=niftyfedora@niftyegg.com \
--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).