From: Jonathan E Brassow <jbrassow@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Re: [Consult-list] dm-multipath has great throughput but we'd like more!
Date: Thu, 18 May 2006 02:36:00 -0500 [thread overview]
Message-ID: <2102bdeb4bf689abbe069a61be3e2a8e@redhat.com> (raw)
In-Reply-To: <20060518072749.GC26035@percy.comedia.it>
On May 18, 2006, at 2:27 AM, Luca Berra wrote:
> On Thu, May 18, 2006 at 08:19:09AM +0100, Bob Gautier wrote:
>> On Thu, 2006-05-18 at 08:05 +0100, Bob Gautier wrote:
>>> Yesterday my client was testing of multipath load balancing and
>>> failover
>>> on a system running ext3 on a logical volume which comprises about
>>> ten
>>> SAN LUNs all reached using multipath in multibus mode over two QL2340
>>> HBAs.
>>
>> Sorry, should have also said: RHEL4u3 x86_64 on DL385 with 16Gb memory
>>
> you could have added the storage model :)
> btw did you do any tuning (i.e. readhaead, scheduler) ?
>
You may also want to do raw through-put testing (lmdd perhaps) to get a
baseline. Certainly, the file system has to be bringing down the
bandwidth somewhat...
brassow
next prev parent reply other threads:[~2006-05-18 7:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 7:05 dm-multipath has great throughput but we'd like more! Bob Gautier
2006-05-18 7:19 ` [Consult-list] " Bob Gautier
2006-05-18 7:27 ` Luca Berra
2006-05-18 7:36 ` Jonathan E Brassow [this message]
2006-05-18 7:44 ` Luca Berra
2006-05-18 7:25 ` Jonathan E Brassow
2006-05-18 7:44 ` Bob Gautier
2006-05-18 7:55 ` Jonathan E Brassow
2006-05-18 7:59 ` Luca Berra
2006-05-18 8:04 ` [Consult-list] " Nicholas C. Strugnell
2006-05-18 9:42 ` Nicholas C. Strugnell
2006-05-18 10:28 ` Richard Keech
2006-05-22 15:31 ` Ed Wilts
2006-05-18 20:28 ` Steve Lord
2006-05-18 17:00 ` [Consult-list] " Rod Nayfield
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=2102bdeb4bf689abbe069a61be3e2a8e@redhat.com \
--to=jbrassow@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.