Jemalloc Postmortem

1. jemalloc

   1 51 10,184 8.7 C

   

   While I certainly wish that more software would reach a "done" stage, I don't think jemalloc is necessarily there yet. Unfortunately I'm aware of there being bugs in the current version of jemalloc, when run in certain environment configurations, including memory leaks. I know the folks that found it were looking to report it, but I guess that won't happen now.

   Even from a quick look at the open issues, I can see https://github.com/jemalloc/jemalloc/issues/2838, and https://github.com/jemalloc/jemalloc/issues/2815 as two examples, but there's a fair number of issues still open against the repository.

   So that'll leave projects like redis & valkey with some decisions to make.

   1) Keep jemalloc and accept things like memory leak bugs

   2) Fork and maintain their own version of jemalloc.

   3) Spend time replacing it entirely.

   4) Hope someone else picks it up?

2. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

3. imaginary

   2 7 5,883 3.1 Go

   Fast, simple, scalable, Docker-ready HTTP microservice for high-level image processing

   

4. imagor

   3 57 3,685 8.4 Go

   Fast, secure image processing server and Go library, using libvips

   

5. libvips

   4 27 10,471 9.6 C

   A fast image processing library with low memory needs.

   

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

   https://github.com/libvips/libvips/discussions/3019

6. chromium

   5 254 21,178 10.0 C++

   The official GitHub mirror of the Chromium source

   

7. tcmalloc

   6 17 4,814 9.7 C++

   

8. sharp

   7 111 30,818 9.0 JavaScript

   High performance Node.js image processing, the fastest module to resize JPEG, PNG, WebP, AVIF and TIFF images. Uses the libvips library.

   

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

   https://github.com/lovell/sharp/issues/955#issuecomment-5458...

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

9. Stream

   getstream.io featured

   Stream - Scalable APIs for Chat, Feeds, Moderation, & Video. Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.

   

Suggest a related project