For some context on why this release is notable: Jemalloc Postmortem [0]<p>[0] <a href="https://news.ycombinator.com/item?id=44264958">https://news.ycombinator.com/item?id=44264958</a>
> I don’t want to dwell on drama, but it is perhaps worth mentioning that we reached a sad end for jemalloc in the hands of Facebook/Meta even though most of the people involved were acting in good faith.<p>Far from the only case. Trillion dollar companies having sudden interest in your open source project is not necessarily a long term benefit.
And some additional context from a few months ago, building off the postmortem.<p><a href="https://theconsensus.dev/p/2026/04/16/who-even-uses-jemalloc-anyway.html" rel="nofollow">https://theconsensus.dev/p/2026/04/16/who-even-uses-jemalloc...</a>
Also, 7 months ago, <a href="https://github.com/facebook/jemalloc" rel="nofollow">https://github.com/facebook/jemalloc</a> said<p>> Development of Jemalloc will transition back to the original open source
project: <a href="https://github.com/jemalloc/jemalloc" rel="nofollow">https://github.com/jemalloc/jemalloc</a>. Meta’s fork of the Jemalloc
project will be fully archived as part of the transition. We look forward
to continuing the collaboration with the community to drive jemalloc.<p>> See blog post for details:
<a href="https://engineering.fb.com/2026/03/02/data-infrastructure/investing-in-infrastructure-metas-renewed-commitment-to-jemalloc/" rel="nofollow">https://engineering.fb.com/2026/03/02/data-infrastructure/in...</a>
Nice to see jemalloc active again. The long-term health of the upstream project is probably just as important as the allocator improvements themselves.
I always wondered, is it French? "Je m'alloc du memory"
Rather a tradition to call a malloc by the initials of the implementer: Jason Evans malloc (jemalloc), Poul-Henning Kamp malloc (phkmalloc), Doug Lea (dlmalloc).<p>P.S. I also wondered whether systemd had any cultural reference to Système D aka Système Débrouillard, but Pottering does not seem to engage in word play on other occasions, so probably not.
It does<p>> Systemd was launched in April 2010; it adopts various ideas from previous init systems and combines them with a uniform configuration and administration interface. Systemd operates as a background service (daemon) and controls important system configuration tasks including hardware initialisation and the starting of server processes. The developers thought that its name is suitably reminiscent of the French term "système D", an expression that relates to "thinking on your feet" and describes high-speed technical problem-solving abilities such as those displayed by TV action hero MacGyver.<p><a href="https://web.archive.org/web/20121014173559/http://www.h-online.com/open/features/Control-Centre-The-systemd-Linux-init-system-1565543.html" rel="nofollow">https://web.archive.org/web/20121014173559/http://www.h-onli...</a>
damn i always thought it was a french thing, this is blowing my mind
"Yes, it is written systemd, not system D or System D, or even SystemD. And it isn't system d either. Why? Because it's a system daemon, and under Unix/Linux those are in lower case, and get suffixed with a lower case d."<p>Source: <a href="https://brand.systemd.io/" rel="nofollow">https://brand.systemd.io/</a>
you were right, check siblings of your comment.
Fun grammatical fact that I only learned after years of speaking French: when borrowing words from other languages, you usually (not always) take the gender of the equivalent word in French, so technically it would be “de la memory” :)
That's the rule the old geezers at the Academy insist on. But then you have idiotic situations where everyone is using "le" for e.g. the COVID virus, while Academicians cry about the D meaning "Disease", which is feminine, making it "la COVID" in their book. As for all languages, the most important rule is that usage prevails. And that's something we in France still have a hard time integrating into public discourse.
An interesting case is "WiFi", short for "wireless fidelity". "Fidélité sans fil" in French should be feminine, but every technical person says "le WiFi" (masculine) while many (most?) non-technical people intuitively say "la WiFi" (feminine).
Thanks, now my brain will forever read it like that. I'm not even a little bit French.
Memory je Srbia
I use Jemalloc on a project because it has per-thread allocation counters. This lets me not only track what each thread is using, but also restrict workloads by enforcing a memory budget. Since my application is almost completely CPU-bound, I allocate one thread per core and then have some smart scheduling to route requests to the threads. I looked at tcmalloc and mimalloc, and neither had this feature at the time, nor did they seem to have any similar feature that could let me have per-thread heaps, which surprised me.
Related, from three days ago, "Comparison of Malloc() Algorithms":<p>* <a href="https://news.ycombinator.com/item?id=49715318">https://news.ycombinator.com/item?id=49715318</a>
I switched to jemalloc on a sidekiq queue and memory dropped from 8gib to under 1gib<p>There’s a slow memory leak somewhere in my code but with jemalloc it no longer actually matters.<p>Thanks to jemalloc team for this!
does anyone familiar with the art have thoughts on why only tcmalloc switched from thread caches to cpu caches? would it make linux behavior diverge too much from other platforms?
(Not an expert but ...) unless you pin threads to cores, which is not the default and somewhat awkward in Linux for user applications, having a per-thread cache doesn't really make sense as your thread could be moved to another core and then your cache will no longer be local to the physical cache.
i think we agree that per cpu caching seems superior. i’m looking for the other side of this. most allocators seem to have stuck with per thread.
If you use a thread-local data structure, your allocator can pretend that it is running on a single-core, single-task system.<p>If you use a CPU-local data structure, you must handle the case where, mid-way through a call to your allocator, the CPU runs a second thread that makes another call to your allocator (and that, too, can get interrupted by another thread that allocates memory, etc.)<p>That makes thread-local easier to implement and likely faster (it doesn’t require any memory barriers in the fast path)<p>Also, good schedulers try to avoid moving threads between CPUs. The better they manage to do that, the lower the cost of having per thread data structures (there likely still is a price, as there most of the time are more threads than CPUs on a system)
Exactly. You want memory arenas that are hot in <i>this CPU's</i> caches. If your thread moves, its per-thread caches are now elsewhere. Original TCMalloc was developed in the days of 2-4 core servers. Current TCMalloc was an evolution in the context of 32+ core servers.
I think tcmalloc gains on thread churn and oversubscription by going the cpu-cache route on Linux. on other platforms, I am not so sure but that can be offset by say a treiber-stack like setup for cross-thread frees/teardowns. So lesser code for Linux for similar fastpath design I guess.
Ok. Why both the homepage and its Github repo doesn't make a single mention of Jason Evans? I know he stepped down but surely it is at least worst mentioning it?<p>Is Meta still using it and developing it? If not who are the driving force behind it now? I just checked there wasn't a release since 2022 and then we have this now. Something changed?<p>Just wish we have a little bit of context. But it is also great it is continue being maintained. It makes a huge difference for Ruby on Rails Apps.
> Just wish we have a little bit of context<p>See the comment of vocx2tx
It's only mentioned in history: <a href="https://github.com/jemalloc/jemalloc/wiki/Background#history" rel="nofollow">https://github.com/jemalloc/jemalloc/wiki/Background#history</a>
Why is this on the HN front page? Is there something particularly noteworthy about this release?
I upvoted it because I benefit from jemalloc in my stack (RoR) and I am tired of AI taking over HN front page. Let the hacker spirit be back!
Upvoted for the same reason. We would not be able to run our workloads without Jemalloc. Kudos to this awesome piece of software.
You are not alone - my first thought was 'oh, HN is trying to bring back the disappointed hackers'. All this AI hype over every little model update fart is so exhausting and boring …
They resumed development on jemalloc only recently, after years of no releases.
The noted resumption <i>and</i> likely a small amount of halo effect from the <i>Comparison of Malloc() Algorithms</i> thread two / three days ago.<p>- <a href="https://news.ycombinator.com/item?id=49715318">https://news.ycombinator.com/item?id=49715318</a>
I just checked whether it's the first release after Jason Evans stepped down as maintainer, but it isn't. That was the previous release, 5.3.1
jemalloc is something you should be aware of if you do software for a living
In the Before Times, the vast majority of software was written in garbage collected language where a working knowledge of the relative merits of C memory allocators is not useful or particularly relevant.<p>Why would the scads of people writing JavaScript, Java, python, go, rails, etc need to be aware of jemalloc?
Memory allocation behaviour has visible impact also for users of managed languages, and the behaviour of software for end users.<p>In our Python program, a bit of numpy processing of large pictures led to 100 GB not being returned to the OS by glibc's default allocator and the machine running out of memory shortly after. With jemalloc's reliable memory return settings, those problems disappear.
I'm in the same boat, I just switched to using it for Kavita, which only does some basic open Image -> Thumbnail to smaller size -> write to disk when importing new comics/books and on linux, memory could swell to 10GB and never get released. Switched to jemalloc and instantly memory stayed well below 1GB.
Generally yes, but the wording of "instantly" begs for the following pedantic remark:<p>This is controlled by jemalloc settings `dirty_decay_ms`, `muzzy_decay_ms`, and their interaction with `background_thread`.<p>`dirty_decay_ms` currently defaults to 10 seconds, so it's not that instant.<p>That is important e.g. for single-threaded programs that start other programs, such as my Python example: If it starts a subprocess before the 10 seconds elapse after `free()`, Python (and jemalloc) do not run, and get no chance to return memory to the OS.<p>In such cases, either enable `background_thread`, or set the `_decay_` values to `0` to ensure immediate return to the OS upon `free()`. (This costs some performance.)<p>See e.g. <a href="https://github.com/jemalloc/jemalloc/issues/2688" rel="nofollow">https://github.com/jemalloc/jemalloc/issues/2688</a>
Okay but do you think the hordes of JavaScript developers at FANG can just change the browser’s allocator?<p>The number of programmers who are in positions to care about jemalloc vs other malloc is minuscule
>...the vast majority of software was written in garbage collected language<p>and even then recently it costed (us) quite a few months to blame JVM and later the default glibc memory allocator for running out native (not java heap memory) - had to exclude all possible native libs (zlib, zstd via jna), direct buffers, sockets, thread stacks and so on. Changing the malloc to jemalloc solved the issue, even though initially it was done for its debugging capabilities.<p>It's just a great memory allocator.
Because unfortunately, the runtimes belonging to all or at least most of those languages perform a lot better with jemalloc than with the system default.<p>I wish that wasn't the case, but it is.
TL;DR: Because the runtime of most GC:d languages uses malloc for its internal data structures.<p>I work for the runtime team of JPG @ Oracle. We use malloc in Hotspot, quite a lot actually! Providing your JVM with a good malloc can improve the performance of the runtime, both in terms of CPU and memory, by quite a bit.<p>I don't think you need the details, but it's good to be aware that some mallocs are better than others, and there are multiple of them. Being aware of jemalloc is a good way of being aware of the facts I just mentioned :-).
Why? Writing a memory allocator is quite simple, and I'd argue that _everyone_ should write one from scratch for any kind of high performance application. It's also trivial to outperform general purpose allocators that have to satisfy countless constraints. I've written numerous special purpose mallocs that are a) both provably (formally) safer than the standard armada and b) significantly faster (>10x throughput).
Your experience writing memory allocators is irrelevant. The point is that jemalloc is widely used and that’s why it makes sense to be aware of it.
Writing an allocator is simple, you’re correct, but writing an allocator that doesn’t suck is not simple.
I'd happily see performance, latency and stability of your allocators in massively multithreaded, long-living programs with workloads where hundreds or thousands of parallel threads continuously create and destroy short-lived small and medium objects.<p>Writing allocators for domain-specific access patterns is easy. Writing a general-purpose high performing, stable allocator with bounded P99 latency is hard.<p>Give your friend, Dunning–Kruger, some better pills to keep him from speaking through you.
You're correct, but his point is that you don't need to solve the <i>generic</i> problem. Solving the generic problem is very hard. Grug doesn't like solving hard problem. What does grug do? Solve five easy problems. Make an arena for the short-lived objects, reuse the objects, use generic multithreaded malloc for the rest. Grug happy.
I guess the point was that before you consider using a different allocator you should rule out a custom one.<p>And that's rather hard, because a general purpose allocator makes all decisions based only on the requested size. This is a very simple interface and such a tool is worth having. But a custom allocator can both bake in a specific scenario and provide more nuanced interaction.
>massively multithreaded, long-living programs with workloads where hundreds or thousands of parallel threads continuously create and destroy short-lived small and medium objects.<p>My first thought would be to use per thread pool allocators.
>where hundreds or thousands of parallel threads continuously create and destroy short-lived small and medium objects.<p>Should one even want a global, general purpose heap allocator for that? Seems like a crazy idea to even consider.
Not everything needs to be general purpose. Allocation can be as easy as bumping a pointer, and it's hard to beat that.
> Why is this on the HN front page?<p>This question was not necessary. You know the answer, because people upvoted this.
because people like you are too busy whining about it to put up something more interesting