Jemalloc 5.4.0

vocx2tx•about 4 hours ago

For some context on why this release is notable: Jemalloc Postmortem [0]

[0] https://news.ycombinator.com/item?id=44264958

lordnacho•about 2 hours ago

I always wondered, is it French? "Je m'alloc du memory"

jibcage•16 minutes ago

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” :)

sam_lowry_•about 2 hours ago

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.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.

tefkah•about 1 hour ago

damn i always thought it was a french thing, this is blowing my mind

eliaspro•about 1 hour ago

"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."

Source: https://brand.systemd.io/

simonask•about 2 hours ago

Thanks, now my brain will forever read it like that. I'm not even a little bit French.

u8080•38 minutes ago

Memory je Srbia

ksec•about 2 hours ago

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.

aktenlage•about 2 hours ago

> Just wish we have a little bit of context

See the comment of vocx2tx

feldrim•about 1 hour ago

It's only mentioned in history: https://github.com/jemalloc/jemalloc/wiki/Background#history

skavi•about 1 hour ago

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?

rwmj•39 minutes ago

(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.

enduku•43 minutes ago

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.

ZenoArrow•about 4 hours ago

Why is this on the HN front page? Is there something particularly noteworthy about this release?

defrost•about 4 hours ago

The noted resumption and likely a small amount of halo effect from the Comparison of Malloc() Algorithms thread two / three days ago.

- https://news.ycombinator.com/item?id=49715318

ck45•about 4 hours ago

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

aktenlage•about 4 hours ago

They resumed development on jemalloc only recently, after years of no releases.

Jemalloc 5.4.0

⚡ Community Insights

Discussion (36 Comments)Read Original on HackerNews