From: Alexandre Derumier <aderumier@odiso.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH-SERIES v2 qemu, qemu-server, manager 0/1] add tcmalloc support
Date: Tue, 16 May 2023 13:22:07 +0200 [thread overview]
Message-ID: <20230516112210.2756384-1-aderumier@odiso.com> (raw)
This patches series add support for tcmalloc allocator with a new optionnal
tuning option in qemu-server.
tcmalloc improve librbd performance by 30% in latency and iops.
some performance bench results:
malloc: 60k iops 4k randread
tcmalloc : 90k iops 4k randread
a qemu patch is provided, to detect if a different memory allocator than
glibc malloc is loaded through LD_PRELOAD, to avoid the call of malloc_trim().
I don't have seen crash without this patch, but it's safer with it,
and as it's called 3-4x by second, it'll avoid some unnecessary calls.
changelog v2:
- update qemu patch for qemu 8.0
qemu:
Alexandre Derumier (1):
add patch: add memory allocator detection and use malloc_trim for
glibc only
...-and-call-malloc_trim-only-for-glibc.patch | 163 ++++++++++++++++++
debian/patches/series | 1 +
2 files changed, 164 insertions(+)
create mode 100644 debian/patches/pve/0063-detect-allocator-and-call-malloc_trim-only-for-glibc.patch
qemu-server:
Alexandre Derumier (1):
qemu options: add tuning allocator
PVE/QemuServer.pm | 35 +++++++++++++++++++++++++++++++++++
1 file changed, 35 insertions(+)
pve-manager:
Alexandre Derumier (1):
ui: qemu : add tuning option
--
2.30.2
next reply other threads:[~2023-05-16 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 11:22 Alexandre Derumier [this message]
2023-05-16 11:22 ` [pve-devel] [PATCH V2 pve-qemu] add patch: add memory allocator detection and use malloc_trim for glibc only Alexandre Derumier
2023-05-16 11:22 ` [pve-devel] [PATCH qemu-server 1/1] qemu options: add tuning allocator Alexandre Derumier
2023-05-16 11:22 ` [pve-devel] [PATCH pve-manager 1/1] ui: qemu : add tuning option Alexandre Derumier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230516112210.2756384-1-aderumier@odiso.com \
--to=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox