From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 3D5C46B43C for ; Thu, 10 Dec 2020 16:24:16 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 2D89618138 for ; Thu, 10 Dec 2020 16:23:46 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 9C9221812D for ; Thu, 10 Dec 2020 16:23:44 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 6835543818; Thu, 10 Dec 2020 16:23:44 +0100 (CET) From: Stefan Reiter To: pve-devel@lists.proxmox.com Date: Thu, 10 Dec 2020 16:23:38 +0100 Message-Id: <20201210152338.19423-1-s.reiter@proxmox.com> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.034 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [RFC pve-qemu] disable jemalloc X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Dec 2020 15:24:16 -0000 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 --- @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 \ -- 2.20.1