Embed Notice

@BrodieOnLinux There are a handful of related bug reports on their tracker.

https://sourceware.org/bugzilla/show_bug.cgi?id=14827

https://sourceware.org/bugzilla/show_bug.cgi?id=26969

https://sourceware.org/bugzilla/show_bug.cgi?id=30769

https://sourceware.org/bugzilla/show_bug.cgi?id=15321

You'll find a lot of blog articles on the subject, too.

https://www.algolia.com/blog/engineering/when-allocators-are-hoarding-your-precious-memory

https://blog.cloudflare.com/the-effect-of-switching-to-tcmalloc-on-rocksdb-memory-use/

https://www.linkedin.com/blog/engineering/infrastructure/taming-memory-fragmentation-in-venice-with-jemalloc

https://www.softwareatscale.dev/p/run-python-servers-more-efficiently

https://notes.secretsauce.net/notes/2016/04/08_glibc-malloc-inefficiency.html

Many simply result to switching to jemalloc since it handles allocations across multiple threads more efficiently, with less fragmentation.