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
baq 49 minutes ago [-]
jemalloc is something you should be aware of if you do software for a living
stackghost 17 minutes ago [-]
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.
Why would the scads of people writing JavaScript, Java, python, go, rails, etc need to be aware of jemalloc?
rfgplk 46 minutes ago [-]
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).
groomlake 41 minutes ago [-]
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.
stackghost 20 minutes ago [-]
Writing an allocator is simple, you’re correct, but writing an allocator that doesn’t suck is not simple.
HackerThemAll 34 minutes ago [-]
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.
Writing allocators for domain-specific access patterns is easy. Writing a general-purpose high performing, stable allocator with bounded P99 latency is hard.
Give your friend, Dunning–Kruger, some better pills to keep him from speaking through you.
Pannoniae 15 minutes ago [-]
You're correct, but his point is that you don't need to solve the generic 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.
Rendered at 07:49:43 GMT+0000 (Coordinated Universal Time) with Vercel.
[0] https://news.ycombinator.com/item?id=44264958
- https://news.ycombinator.com/item?id=49715318
Why would the scads of people writing JavaScript, Java, python, go, rails, etc need to be aware of jemalloc?
Writing allocators for domain-specific access patterns is easy. Writing a general-purpose high performing, stable allocator with bounded P99 latency is hard.
Give your friend, Dunning–Kruger, some better pills to keep him from speaking through you.