linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Wes <wt75@gazeta.pl>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid10 centos5 vs. centos6 300% worse random write performance
Date: Mon, 12 Aug 2013 14:25:24 -0500	[thread overview]
Message-ID: <520936A4.8070806@hardwarefreak.com> (raw)
In-Reply-To: <loom.20130812T104037-602@post.gmane.org>

On 8/12/2013 3:43 AM, Wes wrote:
> Stan Hoeppner <stan <at> hardwarefreak.com> writes:
> 
> 
>> ~$ cat /sys/block/sda/queue/scheduler
>> [CFQ] noop deadline
>> Wes, yours will show CFQ probably as the default on RHEL/CentOS.  You'll
>> want deadline for best seek and all around performance.  So:
>> ~$ echo deadline > /sys/block/sda/queue/scheduler
>> Add that to an init script or cron entry so it sets on every boot.
>> Barriers are not an issue with this test.
>>
> 
> Thank you all. The issue is now closed.
> RHEL5 was not doing cache flush right. It was only corrected in 2.6.32+
> After removing O_SYNC from seekmark the results are now comparable.

Glad you got it figured out.

> Actually it is hard to find a linux raw device random R/W benchmark tool and

FIO is good for raw IO benchmarking.  Can do file based IO as well.
Very flexible, but maybe a bit complicated for first time users.

> seekmark being the most popular fails when comparing pre and post 2.6.32
> systems (unless you remove O_SYNC).

Dunno about seekmark being the most popular.  I'd never heard of it
until this thread.  I'd have guessed FIO was most popular.  But then
again I don't get out much. ;)

-- 
Stan


      reply	other threads:[~2013-08-12 19:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 10:11 raid10 centos5 vs. centos6 300% worse random write performance Wes
2013-07-25 11:44 ` Mikael Abrahamsson
2013-07-25 12:23   ` Wes
2013-07-25 18:49   ` Wes
2013-07-27 20:22   ` Wes
2013-07-27 21:01     ` Marcus Sorensen
2013-07-28  5:46       ` Stan Hoeppner
2013-08-12  8:43         ` Wes
2013-08-12 19:25           ` Stan Hoeppner [this message]

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=520936A4.8070806@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=wt75@gazeta.pl \
    /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).