From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexandre Derumier <aderumier@odiso.com>
Subject: Re: [pve-devel] [PATCH qemu-server] qemu options: add memory_allocator
Date: Mon, 13 Mar 2023 18:09:16 +0100 [thread overview]
Message-ID: <e35b7a8d-e732-6497-c62c-971a48cf6bcb@proxmox.com> (raw)
In-Reply-To: <20230313101600.1041713-1-aderumier@odiso.com>
Am 13/03/2023 um 11:16 schrieb Alexandre Derumier:
> Add optional memory_allocator.
>
> Default is glibc malloc, tcmalloc is available to improve performance
> of ceph librbd.
Looks ok besides some config/api schema details I'd like to see changed.
>
> Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
> ---
> PVE/QemuServer.pm | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
> index 40be44d..8de6c82 100644
> --- a/PVE/QemuServer.pm
> +++ b/PVE/QemuServer.pm
> @@ -723,6 +723,14 @@ EODESCR
> description => "List of host cores used to execute guest processes, for example: 0,5,8-11",
> optional => 1,
> },
> + memory_allocator => {
kebab-case for new properties please, but actually I'd like to have this nested
in a property string here, e.g.:
tuning => {
optional => 1,
type => 'string',
format => { # <- probably in a $tuning_format variable
allocator => {
# ...
},
}
}
> + optional => 1,
> + type => 'string',
> + enum => [ qw(glibc tcmalloc) ],
system tcmalloc
> + default => 'glibc',
> + description => "Configure qemu process memory allocator. tcmalloc improve performance of ceph librbd",
I'd change this to:
description => "Override the memory allocator used in QEMU via LD_PRELOAD.",
verbose_description => "Override the memory allocator used in QEMU via LD_PRELOAD."
." Using tcmalloc might improve performance if ceph librbd is used.",
." NOTE: you must install the libtcmalloc-minimal4 package first!"
> + optional => 1,
you got "optional" set to true twice
> + },
> };
>
> my $cicustom_fmt = {
> @@ -5909,6 +5917,10 @@ sub vm_start_nolock {
>
> my $run_qemu = sub {
> PVE::Tools::run_fork sub {
> +
> + $ENV{LD_PRELOAD} = "/usr/lib/x86_64-linux-gnu/libtcmalloc.so.4"
> + if $conf->{memory_allocator} && $conf->{memory_allocator} eq 'tcmalloc';
> +
> PVE::Systemd::enter_systemd_scope($vmid, "Proxmox VE VM $vmid", %systemd_properties);
>
> my $tpmpid;
prev parent reply other threads:[~2023-03-13 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 10:16 Alexandre Derumier
2023-03-13 17:09 ` Thomas Lamprecht [this message]
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=e35b7a8d-e732-6497-c62c-971a48cf6bcb@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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