AFAIK, It was mainly for rbd performance, but performance is fixed now
(with glibc from buster).
So, I think we don't need it anymore.
On 10/12/2020 16:23, Stefan Reiter wrote:
jemalloc does not play nice with our Rust library (proxmox-backup-qemu),
specifically it never releases memory allocated from Rust to the OS.
This leads to a problem with larger caches (e.g. for the PBS block driver).
It appears to be related to this GitHub issue:
https://github.com/jemalloc/jemalloc/issues/1398
The background_thread solution seems weirdly hacky, so let's disable
jemalloc entirely for now.
Signed-off-by: Stefan Reiter <s.rei...@proxmox.com>
---
@Alexandre: you were the one to introduce jemalloc into our QEMU builds a long
time ago - does it still provide a measurable benefit? If the performance loss
would be too great in removing it, we could maybe figure out some workarounds as
well.
Its current behaviour does seem rather broken to me though...
debian/rules | 1 -
1 file changed, 1 deletion(-)
diff --git a/debian/rules b/debian/rules
index c73d6a1..57e1c91 100755
--- a/debian/rules
+++ b/debian/rules
@@ -60,7 +60,6 @@ config.status: configure
--enable-docs \
--enable-glusterfs \
--enable-gnutls \
- --enable-jemalloc \
--enable-libiscsi \
--enable-libusb \
--enable-linux-aio \
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
