From: Peter Daum <gator_ml@yahoo.de>
To: linux-lvm@redhat.com
Subject: [linux-lvm] write performance with active snapshot
Date: Sun, 09 Nov 2008 16:46:36 +0100 [thread overview]
Message-ID: <gf70ks$16f$1@ger.gmane.org> (raw)
Hi,
for an application I am just working on it looks like lvm snapshots would
be just what I need as far as functionality is concerned. Unfortunately,
I am experiencing such a massive degradation in performance, that the
result is almost useless.
I'm working on a fairly fast machine (Quadcore, 8GB RAM) with a big
hardware RAID array and lvm2 (Debian Lenny; Linux 2.6.26-1-amd64;
LVM version:2.02.39 (2008-06-27)
Library version: 1.02.27 (2008-06-25)
Driver version: 4.13.0)
Sequentially writing to a file (ext3) on a logical volume, I get a
sustained performance of ~ 250 MB/sec. When I create a snapshot
volume, the write throughput drops to 7-8 MB/secs (on the original
volume; writing to the snapshot I see a significant degradation,
but not nearly, as bad; read performance is o.k.).Is this "normal"
or is there anything I can do to about it?
I looked in this list and searched the WWW but couldn't find any
concrete information on the performance impact of snapshots
(except http://www.nikhef.nl/~dennisvd/lvmcrap.html).
It seems like write performance should probably be less then 1/3
of the original throughput, because every write to the source
volume causes 3 I/O operations plus some overhead for meta data.
More difficult to estimate would be the time lost by additional
head movements. Still, a throughput degradation by a factor of 30
seems pretty extreme.
Any ideas?
Regards,
Peter Daum
next reply other threads:[~2008-11-09 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-09 15:46 Peter Daum [this message]
2008-11-10 15:11 ` [linux-lvm] write performance with active snapshot Larry Dickson
2008-11-10 18:04 ` Stuart D. Gathman
2008-11-11 16:04 ` [linux-lvm] " Peter Daum
2009-01-19 0:17 ` thomas62186218
2009-01-31 14:51 ` Peter Daum
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='gf70ks$16f$1@ger.gmane.org' \
--to=gator_ml@yahoo.de \
--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 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.