From: Joe Thornber <thornber@redhat.com>
To: Jagan Reddy <gjmsreddy@yahoo.com>,
device-mapper development <dm-devel@redhat.com>
Subject: Re: dm-thin vs lvm performance
Date: Fri, 20 Jan 2012 18:07:21 +0000 [thread overview]
Message-ID: <20120120180721.GB12920@ubuntu> (raw)
In-Reply-To: <20120120173333.GA12920@ubuntu>
Jagan,
On Fri, Jan 20, 2012 at 05:33:34PM +0000, Joe Thornber wrote:
> Back to testing ...
Here are my aio-stress results for various devices running on top of a
ramdisk:
| Device stack | M/s |
+------------------------+------+
| raw ramdisk | 5440 |
| linear | 5431 |
| 2 stacked linear | 5304 |
| pool device | 5351 |
| linear stacked on pool | 5243 |
| thin | 5375 |
I also tried the thin test after disabling the block locking in
dm-block-manager.c, and using a 128 entry cache local to the thin
device. Neither made any difference to the 'thin' result.
Things for you to check:
i) Are you benchmarking with a ramdisk, or your flash device? In both
cases I think you need to make sure the device has allocated backing
store before you run any tests. Remember that Discards may well
removing this backing.
ii) You claim that io is getting deferred. This will happen when you do
the initial wipe of the thin device to force provisioning. But for
the aio-stress tests you should get nothing deferred (I instrumented
to confirm this).
- Joe
next prev parent reply other threads:[~2012-01-20 18:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 0:55 dm-thin vs lvm performance Jagan Reddy
2012-01-16 12:42 ` Joe Thornber
2012-01-18 19:30 ` Jagan Reddy
2012-01-20 17:03 ` Joe Thornber
2012-01-20 17:33 ` Joe Thornber
2012-01-20 18:07 ` Joe Thornber [this message]
2012-01-20 21:06 ` Jagan Reddy
2012-01-22 20:24 ` Joe Thornber
2012-01-24 23:58 ` Jagan Reddy
2012-01-27 14:58 ` Joe Thornber
2012-01-28 18:54 ` Jagan Reddy
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=20120120180721.GB12920@ubuntu \
--to=thornber@redhat.com \
--cc=dm-devel@redhat.com \
--cc=gjmsreddy@yahoo.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;
as well as URLs for NNTP newsgroup(s).