linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] about snapshot performance
Date: Sat, 19 Nov 2005 11:10:23 +0100	[thread overview]
Message-ID: <20051119101023.GC30556@redhat.com> (raw)
In-Reply-To: <539807300511190157j5699c837r@mail.gmail.com>

On Sat, Nov 19, 2005 at 05:57:04PM +0800, Lee Rocky wrote:
> 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?

Hrm, this should perform better.

Do you have both origin and snapshot allocated to the same PV ?

It will slow down writes, because on every change to the origin,
an exception takes place and the original content needs to be preserved
(causing additional reads and writes) before the update write is allowed
to go through.

If both go to the same spindle it'll explain what you see.


If this is true, try seperating allocation of the snapshot from
the origin (ie. add PVPath to the snapshot create command).

Of course you need at least 2 PVs in your VG to do that and enough
free space on the second to allocate the snapshot.


> 
> KERNEL 2.6.13
> LVM2 = 2.01.15
> Library : 1.01.05
> Driver version: 4.4.0
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Red Hat GmbH
Consulting Development Engineer                   Am Sonnenhang 11
Cluster and Storage Development                   56242 Marienrachdorf
                                                  Germany
Mauelshagen@RedHat.com                            +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      reply	other threads:[~2005-11-19 10:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-19  9:57 [linux-lvm] about snapshot performance Lee Rocky
2005-11-19 10:10 ` Heinz Mauelshagen [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=20051119101023.GC30556@redhat.com \
    --to=mauelshagen@redhat.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).