Hacker News Reader

indeed! most image processing golang services suggest/use jemalloc

Yep, imgproxy seems to use libvips, that recommends jemalloc. I was checking and this is a funny (not) bug report:

Hello, libvips author here. This is probably the canonical thread about libvips and memory fragmentation, and the funniest graph:

(that specific graph is for switching from glib to the musl memory allocator, but jemalloc gives a very similar result)

Those three all use libvips as the image processing engine, fwiw, so it's maybe not a very wide survey.

libvips is fairly highly threaded and does a lot of alloc/free, so it's challenging for most heap implementations.

We use libvips as well sir. We can't overstate how much we benefit from your work!