Re: Why is the performance of my lvmthin snapshot so poor
Demi Marie Obenour <[email protected]>
| Newsgroups | gmane.linux.lvm.general |
|---|---|
| Message-ID | <YqoLTvinIjf9BetH@itl-email> |
On Wed, Jun 15, 2022 at 02:40:29PM +0200, Gionatan Danti wrote: > Il 2022-06-15 11:46 Zhiyong Ye ha scritto: > > I also think it meets expectations. But is there any other way to > > optimize snapshot performance at the code level? Does it help to > > reduce the chunksize size in the code, I see in the help documentation > > that the chunksize can only be 64k minimum. > > I don't think forcing the code to use smaller recordsize is a good idea. > Considering the hard limit on metadata size (16 GB max), 64K chunks are good > for ~16 TB thin pool - already relatively small. > > A, say, 16K recordsize would be good for a 4 TB pool only, an so on. > Moreover, sequential performance will significantly suffer. > > I think you have to accept the performance hit on first chunck allocation & > rewrite. I seriously hope this will be fixed in dm-thin v2. It’s a significant problem for Qubes OS. -- Sincerely, Demi Marie Obenour (she/her/hers) Invisible Things Lab _______________________________________________ linux-lvm mailing list [email protected] https://listman.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEdodNnxM2uiJZBxxxsoi1X/+cIsEFAmKqC04ACgkQsoi1X/+c IsHsww/8DKiqXEV+av94w6dH+2AmoVACfQt5Wv9B/o2cvpXH82IcCN6M+cDFgGwK h+ACxqTORYdjJS+sivYMJoPkmkhJwulF6n/KevBJ4MtFTUrAkYC1J5vRraYTz82Q zHuAzernVlzZs39RIiHjHVOLsDIpXuzXqtxi//6oXLX4nIaHGhNwWj7kvXhU/zLt KQLk/yiv1SewaaAHTaktBKEzk+sk4eXxoJpe9aL50vlKyqKJQIs7m3eAq7n0HCc0 lzQD5VF9J3vaUr6wQoFNp4GQpe3b3DMhkvjBrTC1ilE0Dq2EBXRlLbvx6GXybQ1L CxP8A7vkO3M9vJgfXf6mEGbeF8MJfaELoLtiCADamXL05ZMZXQI//GhasDaK1d4Z cMkjsJaLi/fB/eL587kL4n99e3AoNG+JUrmQoCxd/E8Hdh3d1O8524tC6QGDfVku wyPnxuhAOBEg96bexEy+RDzOguWzm6AKD5zRqemXWw0otEwj86R/IpsIPXRNAFO8 +jKXqp3ZDKWptBCHmwaiVQTS3Fj/mjnIGu3KYHPHteLTcgZoGIJq5a7RargJptZF S1lgewfHY/XhZOutaSGYMO9bQ5NA4BVo+pSJl4yo+rVHc8IRT1oQQzrx1Sr57Qrt TcMhkV5sVkDnwzicCF0rMm+Y3beNTUOjUSY05oQuDXUYLr2Vqog= =yeGt -----END PGP SIGNATURE-----