From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-4.1 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.1 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id 79FF21F597 for ; Sun, 29 Jul 2018 07:46:07 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 18C78120996; Sun, 29 Jul 2018 16:46:04 +0900 (JST) Received: from o1678916x28.outbound-mail.sendgrid.net (o1678916x28.outbound-mail.sendgrid.net [167.89.16.28]) by neon.ruby-lang.org (Postfix) with ESMTPS id AF81E120993 for ; Sun, 29 Jul 2018 16:46:01 +0900 (JST) Received: by filter0045p3mdw1.sendgrid.net with SMTP id filter0045p3mdw1-7935-5B5D70B5-2A 2018-07-29 07:45:57.77539176 +0000 UTC m=+293061.548179347 Received: from herokuapp.com (ec2-54-205-255-87.compute-1.amazonaws.com [54.205.255.87]) by ismtpd0042p1mdw1.sendgrid.net (SG) with ESMTP id mD2RourCRWWpDW7KYScETw Sun, 29 Jul 2018 07:45:57.722 +0000 (UTC) Date: Sun, 29 Jul 2018 07:45:58 +0000 (UTC) From: fweimer@redhat.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 63542 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 14718 X-Redmine-Issue-Author: mperham X-Redmine-Sender: fweimer X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS5tZyPFlcJPlPv1k6AdtcD0k2JMWy69DuE86M JqisMg7mnrL3O3FIJxvGgB57kl+LHpFOlNuSedP1R0tGc2ygcs9EVKp6R6aomptXyXgoww4GabAFyY arxGiBltW2SqfjytC9lsiPFwKx0mO+OZLG0ZZI3JTBVOk3uUGOxcQrQNrA== X-ML-Name: ruby-core X-Mail-Count: 88163 Subject: [ruby-core:88163] [Ruby trunk Feature#14718] Use jemalloc by default? X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #14718 has been updated by fweimer (Florian Weimer). I believe this has been reported multiple times against glibc, without ever mentioning Ruby. The most relevant upstream bug seems to be: https://sourceware.org/bugzilla/show_bug.cgi?id=14581 The Ruby allocator calls posix_memalign (16384, 16344), and unfortunately, such allocations, when freed, can not always be reused for subsequent allocations because the glibc allocator will not search for existing unused aligned allocations of a given size. ---------------------------------------- Feature #14718: Use jemalloc by default? https://bugs.ruby-lang.org/issues/14718#change-73188 * 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/