3 ms·

I've seen this play out before. The history of jemalloc, particularly how it rapidly outpaced virtually every other allocator while under development at Faceboo

I've seen this play out before. The history of jemalloc, particularly how it rapidly outpaced virtually every other allocator while under development at Facebook, suggests otherwise. At this point jemalloc is so good that there is little reason other than NIH to use anything else (unless you want an especially hardened allocator for security and are willing to give up some performance). Even Google uses it in Android. Zstandard is likewise deservedly on track to dominate the lossless compression space.

vthriller 8y ago
> At this point jemalloc is so good Some folks disagree: > [Ruby's] memory usage only reduces when using jemalloc 3; memory usage is still high when using jemalloc 5. Nobody knows why, so that makes the choice of defaulting to jemalloc very dodgy. via https://www.joyfulbikeshedding.com/blog/2019-03-29-the-status-of-ruby-memory-trimming-and-how-you-can-help-with-testing.html https://www.joyfulbikeshedding.com/blog/2019-03-29-the-statu...