From: David Wysochanski <davidw@netapp.com>
To: christophe.varoqui@free.fr,
device-mapper development <dm-devel@redhat.com>
Subject: Re: default value for rr_min_io too high?
Date: Wed, 01 Feb 2006 13:30:22 -0500 [thread overview]
Message-ID: <43E0FE3E.3050402@netapp.com> (raw)
In-Reply-To: <1137801470.18191.16.camel@zezette>
Christophe Varoqui wrote:
> On mer, 2006-01-18 at 23:29 +0100, Christophe Varoqui wrote:
> > On mer, 2006-01-18 at 16:41 -0500, David Wysochanski wrote:
> > > I'm wondering where the value of 1000 came from, and
> > > whether that's really a good default.
> > >
> > > Some preliminary tests I've run with iSCSI seem to indicate
> > > something lower (say 100) might be a better default, but
> > > perhaps others have a differing opinion. I searched the
> > > list but couldn't find any discussion on it.
> > >
> > I'm not really focused on performance, but this seems to be an
> > io-pattern dependant choice.
> >
> > Higher values may help the elevators, (right ?) thus help the seeky
> > workloads. Lower values may certainly benefit from lower values to
> > really get the paths summed bandwidth.
> >
> > Anyway, I can not back this with numbers. Any value will be fine with me
> > as a default, and I highlight that now you can also set per device
> > defaults like rr_min_io in hwtable.c
> >
> Replying to myself,
>
> I finally got the chance to challenge my sayings, and I'm proven badly
> wrong :/
>
> On a StorageWorks EVA110 FC array, 2 active 2Gb/s paths to 2 2Gb/s
> target ports. 1 streaming read (sg_dd dio=1 if=/dev/mapper/mpath0
> of=/dev/null bs=1M count=100k) :
>
> rr_min_io = 1000 => aggregated throughput = 120 Mo/s
> rr_min_io = 100 => aggregated throughput = 130 Mo/s
> rr_min_io = 50 => aggregated throughput = 200 Mo/s
> rr_min_io = 20 => aggregated throughput = 260 Mo/s
> rr_min_io = 10 => aggregated throughput = 300 Mo/s
>
What I seemed to see what the larger the I/O size the lower
I needed to go with rr_min_io to get best throughput. Did
you run it with a smaller block size, say 4k?
I will try to get some more definitive #'s and post.
next prev parent reply other threads:[~2006-02-01 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 21:41 default value for rr_min_io too high? David Wysochanski
2006-01-18 22:29 ` Christophe Varoqui
2006-01-20 23:57 ` Christophe Varoqui
2006-02-01 18:30 ` David Wysochanski [this message]
2006-03-15 16:19 ` David Wysochanski
2006-01-22 17:43 ` Alasdair G Kergon
2006-02-03 16:33 ` Christophe Varoqui
2006-02-04 9:37 ` Christophe Varoqui
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=43E0FE3E.3050402@netapp.com \
--to=davidw@netapp.com \
--cc=christophe.varoqui@free.fr \
--cc=dm-devel@redhat.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