From: Leonid Podolny <leonid.podolny@xtremio.com>
To: dm-devel@redhat.com
Subject: multipath performance problem
Date: Thu, 17 Mar 2011 15:08:01 +0200 [thread overview]
Message-ID: <4D8207B1.1060005@xtremio.com> (raw)
Hi,
I'm not sure it's a correct place to write to, but I'm having a weird issue with the multipath which I'm unable to solve on my own.
There is a SAN device that exports each LUN 8 times. I measure performance using btest (http://http://sourceforge.net/projects/btest/). Basically, it writes 4kb chunks of data from multiple threads and gathers statistics -- throughput in IOPs, average latency and such.
When I compare results of writing into /dev/sdXXX's vs. writing into /dev/dm-XXX's, I see that the multipath devices have about 4 times worse throughput (in IOPs), but about 2 times less latency. In addition, the SAN device allows to see how many commands are currently being processed, and when I work via multipath, this number is many times lower.
All the above shows that I am unable to properly saturate the SAN device when working through multipath. I tried disabling the queue in multipathd. What do I miss?
--
Cheers, L.
reply other threads:[~2011-03-17 13:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D8207B1.1060005@xtremio.com \
--to=leonid.podolny@xtremio.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox