From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Demi Marie Obenour <demi@invisiblethingslab.com>
Subject: Re: [linux-lvm] LVM performance vs direct dm-thin
Date: Sat, 29 Jan 2022 22:32:52 +0100 [thread overview]
Message-ID: <6da8a7fc-4ca4-9c1d-c547-dcba827c5c99@gmail.com> (raw)
In-Reply-To: <YfWkwtOTFYxDyYrW@itl-email>
Dne 29. 01. 22 v 21:34 Demi Marie Obenour napsal(a):
> How much slower are operations on an LVM2 thin pool compared to manually
> managing a dm-thin target via ioctls? I am mostly concerned about
> volume snapshot, creation, and destruction. Data integrity is very
> important, so taking shortcuts that risk data loss is out of the
> question. However, the application may have some additional information
> that LVM2 does not have. For instance, it may know that the volume that
> it is snapshotting is not in use, or that a certain volume it is
> creating will never be used after power-off.
>
Hi
Short answer: it depends ;)
Longer story:
If you want to create few thins per hour - than it doesn't really matter.
If you want to create few thins in a second - than the cost of lvm2 management
is very high - as lvm2 does far more work then just sending a simple ioctl
(as it's called logical volume management for a reason)
So brave developers may always write their own management tools for their
constrained environment requirements that will by significantly faster in
terms of how many thins you could create per minute (btw you will need to also
consider dropping usage of udev on such system)
It's worth to mention - the more bullet-proof you will want to make your
project - the more closer to the extra processing made by lvm2 you will get.
However before you will step into these waters - you should probably evaluate
whether thin-pool actually meet your needs if you have that high expectation
for number of supported volumes - so you will not end up with hyper fast
snapshot creation while the actual usage then is not meeting your needs...
Regards
Zdenek
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2022-01-29 21:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 20:34 [linux-lvm] LVM performance vs direct dm-thin Demi Marie Obenour
2022-01-29 21:32 ` Zdenek Kabelac [this message]
2022-01-30 0:32 ` Demi Marie Obenour
2022-01-30 10:52 ` Zdenek Kabelac
2022-01-30 16:45 ` Demi Marie Obenour
2022-01-30 17:43 ` Zdenek Kabelac
2022-01-30 20:27 ` Gionatan Danti
2022-01-30 21:17 ` Demi Marie Obenour
2022-01-31 7:52 ` Gionatan Danti
2022-02-02 2:09 ` Demi Marie Obenour
2022-02-02 10:04 ` Zdenek Kabelac
2022-02-03 0:23 ` Demi Marie Obenour
2022-02-03 12:04 ` Zdenek Kabelac
2022-02-03 12:04 ` Zdenek Kabelac
2022-01-30 21:39 ` Stuart D. Gathman
2022-01-30 22:14 ` Demi Marie Obenour
2022-01-31 21:29 ` Marian Csontos
2022-02-03 4:48 ` Demi Marie Obenour
2022-02-03 12:28 ` Zdenek Kabelac
2022-02-04 0:01 ` Demi Marie Obenour
2022-02-04 10:16 ` Zdenek Kabelac
2022-01-31 7:47 ` Gionatan Danti
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=6da8a7fc-4ca4-9c1d-c547-dcba827c5c99@gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=demi@invisiblethingslab.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 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.