From: Al Boldi <a1426z@gawab.com>
To: JaniD++ <djani22@dynamicweb.hu>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID0 performance question
Date: Fri, 2 Dec 2005 22:53:17 +0300 [thread overview]
Message-ID: <200512022253.17282.a1426z@gawab.com> (raw)
In-Reply-To: <041e01c5f605$6a7c0830$0400a8c0@dcccs>
JaniD++ wrote:
> > > > > > But the cat /dev/md31 >/dev/null (RAID0, the sum of 4 nodes)
> > > > > > only makes ~450-490 Mbit/s, and i dont know why....
> > > > > >
> > > > > > Somebody have an idea? :-)
> > > > >
> > > > > Try increasing the read-ahead setting on /dev/md31 using
> > > > > 'blockdev'. network block devices are likely to have latency
> > > > > issues and would benefit from large read-ahead.
> > > >
> > > > Also try larger chunk-size ~4mb.
>
> But i don't know exactly what to try.
> increase or decrease the chunksize?
> In the top layer raid (md31,raid0) or in the middle layer raids (md1-4,
> raid1) or both?
>
What I found is that raid over nbd is highly max-chunksize dependent, due to
nbd running over TCP. But increasing chunksize does not necessarily mean
better system utilization. Much depends on your application request size.
Tuning performance to maximize cat/dd /dev/md# throughput may only be
suitable for a synthetic indication of overall performance in system
comparisons.
If your aim is to increase system utilization, then look for a good benchmark
specific to your application requirements which would mimic a realistic
load.
--
Al
next prev parent reply other threads:[~2005-12-02 19:53 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 [this message]
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++
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=200512022253.17282.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=djani22@dynamicweb.hu \
--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).