From: "JaniD++" <djani22@dynamicweb.hu>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID0 performance question
Date: Tue, 22 Nov 2005 02:56:26 +0100 [thread overview]
Message-ID: <00fd01c5ef07$f41bf690$a700a8c0@dcccs> (raw)
In-Reply-To: 17320.45715.533255.759042@cse.unsw.edu.au
----- Original Message -----
From: "Neil Brown" <neilb@suse.de>
To: "JaniD++" <djani22@dynamicweb.hu>
Cc: "Al Boldi" <a1426z@gawab.com>; <linux-raid@vger.kernel.org>
Sent: Wednesday, December 21, 2005 2:40 AM
Subject: Re: RAID0 performance question
> On Sunday December 18, djani22@dynamicweb.hu wrote:
> >
> > The raid (md) device why dont have scheduler in sysfs?
> > And if it have scheduler, where can i tune it?
>
> raid0 doesn't do any scheduling.
> All it does is take requests from the filesystem, decide which device
> they should go do (possibly splitting them if needed) and forwarding
> them on to the device. That is all.
>
> > The raid0 can handle multiple requests at one time?
>
> Yes. But raid0 doesn't exactly 'handle' requests. It 'directs'
> requests for other devices to 'handle'.
>
> >
> > For me, the performance bottleneck is cleanly about RAID0 layer used
exactly
> > as "concentrator" to join the 4x2TB to 1x8TB.
> > But it is only a software, and i cant beleave it is unfixable, or
> > tunable.
>
> There is really nothing to tune apart from chunksize.
>
> You can tune the way the filesystem/vm accesses the device by setting
> readahead (readahead on component devices of a raid0 has exactly 0
> effect).
First i want to sorry, about "Neil not interested" thing in previous mail...
:-(
I have already try the all available options, including readahead in all
layer (result in earlyer mails), and chunksize.
But with this settings, i cannot workaround this.
And the result is incomprehensible for me!
The raid0 performance is not equal with one component , with sum of all
component , and not equal with the slowest component!
>
> You can tune the underlying devices by choosing a scheduler (for a
> disk drive) or a packet size (for over-the-network devices) or
> whatever.
The NBD has a scheduler, and this is already tuned for really top
performance, and for the components it is really great! :-)
(I have planned to set the NBD to 4KB packets, but this is hard, becaused by
my NICs are not supported the jumbo packets...)
>
> But there is nothing to tune in raid0.
>
>
> Also, rather than doing measurements on the block devices (/dev/mdX)
> do measurements on a filesystem created on that device.
> I have often found that the filesystem goes faster than the block
> device.
I use XFS, and the two performance is almost equal, depends on kind of load.
But in most often case, it is almost equal.
Thanks,
Janos
>
>
> NeilBrown
next prev parent reply other threads:[~2005-11-22 1:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 19:34 mdadm 2.1: command line option parsing bug? Andreas Haumer
2005-11-21 23:21 ` Neil Brown
2005-11-22 11:21 ` Michael Tokarev
2005-11-24 5:15 ` Neil Brown
2005-11-22 15:41 ` Molle Bestefich
2005-11-24 5:25 ` Neil Brown
2005-11-24 7:31 ` Ross Vandegrift
2005-12-15 1:53 ` Molle Bestefich
2005-12-15 4:19 ` Neil Brown
2005-12-15 10:37 ` Molle Bestefich
2005-11-22 22:05 ` Andre Noll
2005-11-26 14:04 ` RAID0 performance question JaniD++
2005-11-26 15:56 ` Raz Ben-Jehuda(caro)
2005-11-26 16:08 ` JaniD++
2005-11-26 17:11 ` Lajber Zoltan
2005-11-26 17:34 ` JaniD++
2005-11-26 19:47 ` Lajber Zoltan
2005-11-26 23:27 ` Neil Brown
2005-11-26 23:37 ` JaniD++
2005-11-27 15:39 ` Al Boldi
2005-11-27 16:21 ` JaniD++
2005-11-27 17:40 ` Al Boldi
2005-11-27 19:02 ` JaniD++
2005-11-30 23:13 ` JaniD++
2005-12-02 19:53 ` Al Boldi
2005-12-18 0:13 ` JaniD++
2005-12-19 11:16 ` Al Boldi
2005-11-22 1:14 ` JaniD++
2005-11-23 10:48 ` JaniD++
2005-12-21 1:40 ` Neil Brown
2005-11-22 1:56 ` JaniD++ [this message]
2005-12-22 4:49 ` Neil Brown
2005-11-23 9:44 ` JaniD++
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='00fd01c5ef07$f41bf690$a700a8c0@dcccs' \
--to=djani22@dynamicweb.hu \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).