archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <>
To: LVM general discussion and development <>,
	Zhiyong Ye <>
Subject: Re: [linux-lvm] The feasibility of implementing an alternative snapshot approach
Date: Wed, 4 Jan 2023 15:09:32 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Dne 04. 01. 23 v 9:00 Zhiyong Ye napsal(a):
> Dear all,
> The current standard lv implementation of snapshots is COW (Copy-on-write), 
> which creates snapshots very quickly. However, the first write performance of 
> the original lv will be poor after creating a snapshot because of COW. 
> Moreover, the more snapshots there are, the worse the performance of the 
> original lv will be.
> I tested the random read/write performance when the original lv was created 
> with different number of snapshots. The data is shown below:
> Number of snapshots  Randread(iops)  Randwrite(iops)
>          0                21989           22034
>          1                10048           10041
>          2                6770            6773
>          3                5375            5378
> There are scenarios where the performance of the original lv is more 
> demanding, and the speed of snapshot creation is not as strong a requirement. 
> Because it is the original lv that will actually be used, and the snapshot is 
> only a secondary function. Therefore snapshots using the COW approach will not 
> meet the needs of this scenario.
> Therefore, is it feasible to implement another way of taking snapshots? Let's 
> say the first snapshot is created as a full snapshot, and all subsequent 
> snapshots are based on incremental data from the previous snapshot.


Have you played with thin provisioning - as that's the answer to the slow 



linux-lvm mailing list
read the LVM HOW-TO at

  reply	other threads:[~2023-01-04 14:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04  8:00 [linux-lvm] The feasibility of implementing an alternative snapshot approach Zhiyong Ye
2023-01-04 14:09 ` Zdenek Kabelac [this message]
2023-01-04 16:12   ` Zhiyong Ye
2023-01-06 13:42     ` Zdenek Kabelac
2023-01-09  6:21       ` Zhiyong Ye
2023-01-09 22:18         ` Zdenek Kabelac
2023-01-10  3:48           ` [linux-lvm] [External] " Zhiyong Ye

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).