From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
"k.chai@proxmox.com" <k.chai@proxmox.com>
Cc: "tchaikov@gmail.com" <tchaikov@gmail.com>
Subject: Re: [RFC] Re-enable alternative memory allocator (tcmalloc) for pve-qemu?
Date: Thu, 26 Mar 2026 06:09:30 +0000 [thread overview]
Message-ID: <623789cf45105fd421fe32f32562538fb76d07a8.camel@groupe-cyllene.com> (raw)
In-Reply-To: <DHCDIFA0P8QP.2CTY4G4EEGKQ0@proxmox.com>
Hi Kefu !
>>1. Does anyone remember why tcmalloc was removed after only 8 days
>> in 2015 (2.3-4)? The changelog just says "remove tcmalloc" with
>> no explanation.
If I remember, it was because I had lower peformance than jemalloc
because of too low default TCMALLOC_MAX_TOTAL_THREAD_CACHE_BYTES &&
also the tcmalloc 2.2 at this time. (it was resolved later with
tcmalloc 2.4)
See:
https://lists.proxmox.com/pipermail/pve-devel/2015-June/015551.html
next prev parent reply other threads:[~2026-03-26 6:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 2:54 Kefu Chai
2026-03-26 6:09 ` DERUMIER, Alexandre [this message]
2026-03-26 6:16 ` Dietmar Maurer
2026-03-26 7:48 ` 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=623789cf45105fd421fe32f32562538fb76d07a8.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.com \
--cc=k.chai@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=tchaikov@gmail.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