From: Matthieu Patou <mat@matws.net>
To: Asdo <asdo@shiftmail.org>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Random IO with md raid
Date: Tue, 08 Dec 2009 01:59:30 +0300 [thread overview]
Message-ID: <4B1D88D2.9000001@matws.net> (raw)
In-Reply-To: <4B1A6C28.20800@shiftmail.org>
On 05/12/2009 17:20, Asdo wrote:
> Matthieu Patou wrote:
>> * 1 raid 1 volume of 2 1TB hard drive
> Are these drives also on the 3ware?
I suppose that you are speaking of the 2 single drives. If so yes they
are also connected to the 3ware controller, they are not exported as
jbod but as seperate hard drives.
Are they exported as jbod?
>> * 2 single volume of 1 TB hard drive each
>> ...
>> Does anyone has an any idea ?
>
> Try anticipatory, deadline and noop schedulers on disks (not CFQ)
> Try setting readahead to exactly 4K, or set it to lowest possible value
I tried all the different scheduler both with 4K and with the default
value and I still have raid1 software that do 1/2 or 1/3 of the raid1
hardware for random write I/O.
> (I'm not sure what is best), since this is random access...
> Increase stripe_cache_size as high as you can, p
So for raid1 there is no stripe_cache_size so I didn't set it ...
> Let us/me know the results afterwards...
I also made a simple tests with the CFQ scheduler without any other
tunning but turning of the controller cache and at this moment the
results of the RAID1 hardware and the RAID1 software are very close.
Looks like linux is not able to use the onboard cache of controller as
efficiently as the 3ware controller it self at least for random IO.
Any other ideas ?
Matthieu
next prev parent reply other threads:[~2009-12-07 22:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 22:31 Random IO with md raid Matthieu Patou
2009-12-05 14:20 ` Asdo
2009-12-07 22:59 ` Matthieu Patou [this message]
2009-12-09 16:36 ` Goswin von Brederlow
2009-12-14 9:06 ` Matthieu Patou
2009-12-14 10:13 ` Michael Evans
2009-12-16 11:32 ` Goswin von Brederlow
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=4B1D88D2.9000001@matws.net \
--to=mat@matws.net \
--cc=asdo@shiftmail.org \
--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).