From: dennisb55@... Date: 2018-05-14T06:42:52+00:00 Subject: [ruby-core:87016] [Ruby trunk Feature#14718] Use jemalloc by default? Issue #14718 has been updated by bluz71 (Dennis B). shyouhei (Shyouhei Urabe) wrote: > You can explicitly specify `--with-jemalloc`, for a long time. I don't see any practical reason why that's insufficient. I can turn it default on. Anything beyond that requires a good reason to do so, not just "everybody else is jumping off the ridge" thing. Turning on `--with-jemalloc` by default for the Linux platform achieves the desired result we want. I will be more than pleased if this is the final result. Can you do this? Note, this will be a new build time dependency on Linux which should not be an issue since all major Linux distributions will provide the jemalloc library and development packages in their base repositories (`libjemalloc-dev` for Debian-based systems). > Please. I want to make the situation better. Why do we have to bundle 3rd-party source codes? Correct, no bundling is strictly required, it just offered a known-quantity since different jemalloc versions will be shipped with the various Linux distributions. I still believe a `--without-jemalloc` option should be provided as an escape hatch. Also, if this change happens then we should contact the various Ruby build/version systems (rvm, rbenv and chruby/ruby-install) about this since they should change their auto-install-dependency engines to also include jemalloc (on Linux). I can do all that if the default changes. If this change happens for Ruby 2.6 I genuinely believe that very many long-lived Ruby-based applications will benefit from this change. ---------------------------------------- Feature #14718: Use jemalloc by default? https://bugs.ruby-lang.org/issues/14718#change-71982 * Author: mperham (Mike Perham) * Status: Open * Priority: Normal * Assignee: * Target version: ---------------------------------------- I know Sam opened #9113 4 years ago to suggest this but I'm revisiting the topic to see if there's any movement here for Ruby 2.6 or 2.7. I supply a major piece of Ruby infrastructure (Sidekiq) and I keep hearing over and over how Ruby is terrible with memory, a huge memory hog with their Rails apps. My users switch to jemalloc and a miracle occurs: their memory usage drops massively. Some data points: https://twitter.com/brandonhilkert/status/987400365627801601 https://twitter.com/d_jones/status/989866391787335680 https://github.com/mperham/sidekiq/issues/3824#issuecomment-383072469 Redis moved to jemalloc many years ago and it solved all of their memory issues too. Their conclusion: the glibc allocator "sucks really really hard". http://oldblog.antirez.com/post/everything-about-redis-24.html This is a real pain point for the entire Rails community and would improve Ruby's reputation immensely if we can solve this problem. -- https://bugs.ruby-lang.org/ Unsubscribe: