From: "chris (fool) mccraw" <gently@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] advice for curing terrible snapshot performance?
Date: Mon, 15 Nov 2010 10:18:49 -0800 [thread overview]
Message-ID: <AANLkTinkUaiFrOAr48JhJJaixGcpK0REmLXgK_t2Mb7D@mail.gmail.com> (raw)
In-Reply-To: <4CE1770B.8000007@q7.com>
On Mon, Nov 15, 2010 at 10:08, Joe Pruett <joey@q7.com> wrote:
>
>>> BTW, rewriting that 1G file would be normal speed, since
>>> the modified chunks have already been copied to the snapshot.
>> i'd think that, and you'd think that, but it is not the case. �most of
>> my tests were done by rewriting the file 4x, and while the snap %used
>> (monitored with the 'lvs' command) doesn't keep going up, performance
>> stays the same.
>>
> i did similar tests and i saw that even though i was rewriting the file,
> it appeared that the ext3 layer was reallocating new blocks. �the
> snapshot usage would increase to show 3x the number of blocks i had
> thought it should have touched, and then it seemed to stay stable. �this
> is one of the problems with a block level (as opposed to file level)
> snapshot.
interestingly, xfs does not show the usage increase as sharply
(IIRC--i stopped checking that number after a few runs), but neither
is the performance better.
next prev parent reply other threads:[~2010-11-15 18:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 21:52 [linux-lvm] advice for curing terrible snapshot performance? chris (fool) mccraw
2010-11-12 22:28 ` Joe Pruett
2010-11-12 23:30 ` chris (fool) mccraw
2010-11-12 23:36 ` Joe Pruett
2010-11-13 0:17 ` chris (fool) mccraw
2010-11-13 0:58 ` Stuart D Gathman
2010-11-15 17:52 ` chris (fool) mccraw
2010-11-15 18:04 ` Romeo Theriault
2010-11-15 18:08 ` Joe Pruett
2010-11-15 18:18 ` chris (fool) mccraw [this message]
2010-11-15 23:51 ` Stuart D. Gathman
2010-11-16 0:09 ` chris (fool) mccraw
2010-11-15 18:05 ` chris (fool) mccraw
2010-11-15 14:35 ` Romeo Theriault
2010-11-15 17:46 ` chris (fool) mccraw
2010-11-15 20:37 ` Stephane Chazelas
2010-11-15 22:57 ` Stuart D. Gathman
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=AANLkTinkUaiFrOAr48JhJJaixGcpK0REmLXgK_t2Mb7D@mail.gmail.com \
--to=gently@gmail.com \
--cc=linux-lvm@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;
as well as URLs for NNTP newsgroup(s).