From: Eneko Lacunza
Signed-off-by: Eneko Lacunza
---
.../0054-vma-force-enable-rbd-cache-for-qmrestore.patch | 17 +
debian/patches/series | 1 +
2 files changed, 18 insertions(+)
create mode 100644
debian/patches/pve/0054-vma-force-enable-rb
From: Eneko Lacunza
Signed-off-by: Eneko Lacunza
---
debian/patches/pve/0055-vma-restore-set-cache-unsafe.patch | 14 ++
debian/patches/series | 1 +
2 files changed, 15 insertions(+)
create mode 100644 debian/patches/pve/0055-vma-restore-set-c
This patch is a follow-up to Alexandre's rbd patch, so that we set cache
unsafe during restore for performance. This is the same done in qemu-img
convert, which defaults to unsafe cache.
In our fixed ceph cluster this has given us a x4 boost (from 15MB/s to
94MB/s) with a 44% sparse 10GB backup (
From: Eneko Lacunza
Signed-off-by: Eneko Lacunza
---
.../0054-vma-force-enable-rbd-cache-for-qmrestore.patch | 17 +
debian/patches/series | 1 +
2 files changed, 18 insertions(+)
create mode 100644
debian/patches/pve/0054-vma-force-enable-rb
This time this is generated against git repo.
Patch issues a "bogus" flush after opening restore destination device to enable
rbd cache (writeback/coalescing)
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/lis
