From: Jon Bernard <jbernard@tuxion.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: dm-devel@redhat.com
Subject: Re: poor thin performance, relative to thick
Date: Fri, 15 Jul 2016 16:57:21 -0400 [thread overview]
Message-ID: <20160715205721.GA4948@helmut> (raw)
In-Reply-To: <20160715185906.GA29580@redhat.com>
* Mike Snitzer <snitzer@redhat.com> wrote:
> On Thu, Jul 14 2016 at 12:21am -0400,
> Jon Bernard <jbernard@tuxion.com> wrote:
>
> > Do you have any intuition on where to start looking?
>
> Joe asked me a very basic/obvious question: is block zeroing enabled?
> (block zeroing is enabled by default -- you have to know to disable it)
Ah, I failed to mention that I did read about that in the manpage and
disabled it. Just to be sure, here is my lvs output:
# lvs -o +zero
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert Zero
pool1 thin twi-aot--- 1.00t 9.77 0.35
pool2 thin twi-aot--- 1.00t 0.00 0.03
thick thin -wi-a----- 100.00g unknown
thindisk1 thin Vwi-a-t--- 100.00g pool1 100.00 unknown
I believe we'd see a 'z' in attr field if it were enabled.
> If zeroing wasn't disabled that could explain some of the sizable
> performance differences. Please use/test the 'skip_block_zeroing'
> feature if you aren't already (also see the "Zeroing' section of the
> 'lvmthin' manpage).
If my understanding is correct, even with zeroing enabled, my initial
sequential write that that caused the volume to become fully allocated
would have alleviated any further zeroing during the random write test.
--
Jon
prev parent reply other threads:[~2016-07-15 20:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 20:44 poor thin performance, relative to thick Jon Bernard
2016-07-12 8:28 ` Jack Wang
2016-07-13 3:29 ` Jon Bernard
2016-07-13 14:17 ` Mike Snitzer
2016-07-12 8:30 ` Zdenek Kabelac
2016-07-13 4:00 ` Jon Bernard
2016-07-12 18:46 ` Mike Snitzer
2016-07-14 4:21 ` Jon Bernard
2016-07-14 20:58 ` Mike Snitzer
2016-07-15 18:59 ` Mike Snitzer
2016-07-15 20:57 ` Jon Bernard [this message]
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=20160715205721.GA4948@helmut \
--to=jbernard@tuxion.com \
--cc=dm-devel@redhat.com \
--cc=snitzer@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.