public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>,
	"pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
	"k.chai@proxmox.com" <k.chai@proxmox.com>
Subject: Re: [PATCH pve-qemu 0/2] Re-enable tcmalloc as the memory allocator
Date: Mon, 13 Apr 2026 10:14:57 +0200	[thread overview]
Message-ID: <9db86c5e-d382-4eed-a1fd-905e44a259e1@proxmox.com> (raw)
In-Reply-To: <4628fcc1c283bc4ae80f19e6fe8ae922c0968af9.camel@groupe-cyllene.com>

Am 10.04.26 um 12:44 PM schrieb DERUMIER, Alexandre:
> 
>>> How does the performance change when doing IO within a QEMU guest?
>>>
>>> How does this affect the performance for other storage types, like
>>> ZFS,
>>> qcow2 on top of directory-based storages, qcow2 on top of LVM, LVM-
>>> thin,
>>> etc. and other workloads like saving VM state during snapshot,
>>> transfer
>>> during migration, maybe memory hotplug/ballooning, network
>>> performance
>>> for vNICs?
> 
> Hi Fiona,
> 
> I'm stil running in production (I have keeped tcmalloc after the
> removal some year ago from the pve build), and I didn't notice problem.
> (but I still don't use pbs).
> 
> But I never have done bench with/without it since 5/6 year.
> 
> Maybe vm memory should be checked too, I'm thinking about RSS memory
> with balloon free_page_reporting, to see if it's correcting freeing
> memory.

Thanks! If it was running fine for you for this long, that is a very
good data point :) Still, testing different scenarios/configurations
would be nice to rule out that there is a (performance) regression
somewhere else.




  reply	other threads:[~2026-04-13  8:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10  4:30 Kefu Chai
2026-04-10  4:30 ` [PATCH pve-qemu 1/2] PVE: use " Kefu Chai
2026-04-13 13:12   ` Fiona Ebner
2026-04-10  4:30 ` [PATCH pve-qemu 2/2] d/rules: enable " Kefu Chai
2026-04-13 13:13   ` Fiona Ebner
2026-04-13 13:23     ` DERUMIER, Alexandre
2026-04-13 13:40       ` Fabian Grünbichler
2026-04-14  8:10         ` Fiona Ebner
2026-04-10  8:12 ` [PATCH pve-qemu 0/2] Re-enable " Fiona Ebner
2026-04-10 10:45   ` DERUMIER, Alexandre
2026-04-13  8:14     ` Fiona Ebner [this message]
2026-04-13 11:13       ` Kefu Chai
2026-04-13 13:14         ` DERUMIER, Alexandre
2026-04-13 13:18         ` Fiona Ebner
2026-04-14  5:41           ` Kefu Chai
2026-04-14  5:48 ` superseded: " Kefu Chai

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=9db86c5e-d382-4eed-a1fd-905e44a259e1@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=alexandre.derumier@groupe-cyllene.com \
    --cc=k.chai@proxmox.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal