home.social

#jemalloc — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #jemalloc, aggregated by home.social.

  1. TIL about #jemalloc, a scalable concurrent malloc(3) implementation for #FreeBSD and #Linux, only to find out it had its 20th birthday a few days ago! 🎂

    Check out the original paper on papers.freebsd.org/2006/bsdcan

  2. 🥳🎉 Meta's backtracking on #jemalloc is hailed as a #groundbreaking move! Because clearly, the world needed another deep dive into memory allocation strategies over their morning coffee. 🙄🔍 Who knew infrastructure updates could be so riveting?
    engineering.fb.com/2026/03/02/ #Meta #memoryallocation #infrastructureupdates #technews #HackerNews #ngated

  3. 🥳🎉 Meta's backtracking on #jemalloc is hailed as a #groundbreaking move! Because clearly, the world needed another deep dive into memory allocation strategies over their morning coffee. 🙄🔍 Who knew infrastructure updates could be so riveting?
    engineering.fb.com/2026/03/02/ #Meta #memoryallocation #infrastructureupdates #technews #HackerNews #ngated

  4. 🥳🎉 Meta's backtracking on #jemalloc is hailed as a #groundbreaking move! Because clearly, the world needed another deep dive into memory allocation strategies over their morning coffee. 🙄🔍 Who knew infrastructure updates could be so riveting?
    engineering.fb.com/2026/03/02/ #Meta #memoryallocation #infrastructureupdates #technews #HackerNews #ngated

  5. 🥳🎉 Meta's backtracking on #jemalloc is hailed as a #groundbreaking move! Because clearly, the world needed another deep dive into memory allocation strategies over their morning coffee. 🙄🔍 Who knew infrastructure updates could be so riveting?
    engineering.fb.com/2026/03/02/ #Meta #memoryallocation #infrastructureupdates #technews #HackerNews #ngated

  6. 🥳🎉 Meta's backtracking on #jemalloc is hailed as a #groundbreaking move! Because clearly, the world needed another deep dive into memory allocation strategies over their morning coffee. 🙄🔍 Who knew infrastructure updates could be so riveting?
    engineering.fb.com/2026/03/02/ #Meta #memoryallocation #infrastructureupdates #technews #HackerNews #ngated

  7. At $dayjob, we have an embedded #Linux device that is periodically running low on memory. It's using the default (#glibc) allocator.

    No leaks, and lowering MALLOC_MMAP_THRESHOLD_ made the problem go away. So: memory fragmentation.

    With glibc, I'm sure that's no surprise to anyone "Use #jemalloc", right?

    Sure, some do, but I don't want to use a hammer that big without trying to understand the problem first. Jemalloc being effectively end of life also doesn't really thrill me.

    1/5

  8. If you want to understand the life cycle of software, this history of jemalloc is not a bad start

    Remember: there is no bad or good here, and there is no intentionality. To assume there should have been a different outcome would be presumptuous.

    There just “is”. Not everybody understands this.

    https://jasone.github.io/2025/06/12/jemalloc-postmortem/

    #jemalloc #softwareEcosystems #softwareEngineering

  9. Have you ever dealt with this issue? Should I install #jemalloc right away or play detective? Setup: #ruby 2.7.8, #puma 3.12.6.

  10. As my #Friendica server, my-place.social, has grown to some 315 active users in just 5 months, I'm starting to hit up against #mariaDB limitations relating to the default memory manager, #MALLOC. This weekend I'm going to replace it with #jemalloc to reduce stalls, memory fragmentation issues, out-of-memory problems, and instability.

    Friendica puts a lot of pressure on the database, mariaDB in this case, much more than Mastodon apparently does on PostgreSQL. My feeling is that the Mastodon developers have done much better database tuning.

    But, none-the-less, the update must be done. This will be done on an Ubuntu server.

    Does anyone who has changed the MariaDB or mySQL memory manager have any advice to share to keep me out of trouble?

    BTW, #TCMalloc is not an option as other admins have reported crashes using it with Friendica.

  11. Add one more vote for using #jemalloc for #rails applications. This is our memory graph for the #Sidekiq workers.

    Besides adding the linked buildpack and setting configuration options, we had nothing else to do.

    elements.heroku.com/buildpacks

  12. Released ruby-install 0.10.0! This release contains many small improvements to usability and better support for building CRuby with jemalloc or YJIT enabled.

    $ ruby-install ruby -- --with-jemalloc
    $ ruby-install ruby -- --enable-yjit

    github.com/postmodern/ruby-ins
    github.com/postmodern/ruby-ins

    #ruby #rubyinstall #ruby_install #jemalloc #yjit

  13. I just learnt about `jemalloc` in order to fix the memory hunger of Synapse.

    So yeah, Python developers will rather hijack the glibc memory allocator than switch to a resource efficient language.

    #jemalloc #Matrix #Synapse #Python #glibc #programming

  14. progress: #jemalloc built ok. Attempting to build #Ruby 3.2.3. We are getting far, far further with this than we did with Solaris, to the point that this may actually work

  15. progress: have to build #jemalloc from source to allow Ruby to build. Doesn't seem to be a massive problem, which is good

  16. Turns out the jemalloc really works!

    So, in 10ish days of updates we've managed to _halve_ our response times, and do it while using less RAM!

    #ruby #yjit #jemalloc