Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- 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?
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?
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.
by ksec - 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?by skavi
- Nice to see jemalloc active again. The long-term health of the upstream project is probably just as important as the allocator improvements themselves.by ggg011012
- Related, from three days ago, "Comparison of Malloc() Algorithms":by throw0101a
- I switched to jemalloc on a sidekiq queue and memory dropped from 8gib to under 1gib
There’s a slow memory leak somewhere in my code but with jemalloc it no longer actually matters.
Thanks to jemalloc team for this!
- 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.by atombender
- I always wondered, is it French? "Je m'alloc du memory"by lordnacho
- For some context on why this release is notable: Jemalloc Postmortem [0]by vocx2tx