From: Lee Rocky <rocky366@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] about snapshot performance
Date: Sat, 19 Nov 2005 17:57:04 +0800 [thread overview]
Message-ID: <539807300511190157j5699c837r@mail.gmail.com> (raw)
I found some reference that discuss about LVM1 volume with snapshot performance
https://www.redhat.com/archives/linux-lvm/2003-January/msg00173.html
https://www.redhat.com/archives/linux-lvm/2003-January/msg00239.html
and I follow the steps with my LVM2
command
"sync ; time dd if=/dev/zero of=filename bs=1024k count=2000"
the result is
dd write on LV without snapshots = 150MB/s
dd write on LV with 1 snapshots = 4.42 MB/s
I got very slow write performace.
but read has no problem.
is this result work as expected?
KERNEL 2.6.13
LVM2 = 2.01.15
Library : 1.01.05
Driver version: 4.4.0
next reply other threads:[~2005-11-19 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-19 9:57 Lee Rocky [this message]
2005-11-19 10:10 ` [linux-lvm] about snapshot performance Heinz Mauelshagen
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=539807300511190157j5699c837r@mail.gmail.com \
--to=rocky366@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).