[lxc-devel] [lxd/master] Document issue with LXD performance when backed by LVM with a large v…

[leehambley on Github]

A non-text attachment was scrubbed...
Name: not available
Type: text/x-mailbox
Size: 753 bytes
Desc: not available
URL: <http://lists.linuxcontainers.org/pipermail/lxc-devel/attachments/20171127/f2c53004/attachment.bin>
-------------- next part --------------
From 767fcfc2a6a699b824044a44b9e5762520b7a26a Mon Sep 17 00:00:00 2001
From: Lee Hambley <leehambley at harrow.io>
Date: Mon, 27 Nov 2017 16:28:33 +0100
Subject: [PATCH] Document issue with LXD performance when backed by LVM with a
 large volume of archive metadata (high container, volume turnover)

---
 doc/storage-backends.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/doc/storage-backends.md b/doc/storage-backends.md
index c3db7802d..65c716686 100644
--- a/doc/storage-backends.md
+++ b/doc/storage-backends.md
@@ -47,6 +47,7 @@ rsync is used to transfer the container content across.
  - Uses LVs for images, then LV snapshots for containers and container snapshots.
  - The filesystem used for the LVs is ext4 (can be configured to use xfs instead).
  - LVs are created with a default size of 10GiB (can be configured through).
+ - For environments with high container turn over (e.g continuous integration) it may be important to tweak the archival `retain_min` and `retain_days` settings in `/etc/lvm/lvm.conf` to avoid slowdowns when interacting with LXD.
 
 ### ZFS