From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-3.9 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.0 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id 7281D1F42D for ; Fri, 18 May 2018 07:59:32 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 5147D120B53; Fri, 18 May 2018 16:59:30 +0900 (JST) Received: from dcvr.yhbt.net (dcvr.yhbt.net [64.71.152.64]) by neon.ruby-lang.org (Postfix) with ESMTPS id A14A4120B52 for ; Fri, 18 May 2018 16:59:26 +0900 (JST) Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 523A01F42D; Fri, 18 May 2018 07:59:24 +0000 (UTC) Date: Fri, 18 May 2018 07:59:24 +0000 From: Eric Wong To: ruby-core@ruby-lang.org Message-ID: <20180518075924.GA17095@dcvr> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-ML-Name: ruby-core X-Mail-Count: 87164 Subject: [ruby-core:87164] Re: [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" dennisb55@hotmail.com wrote: > P.S. I doubt that glibc will ever be *fixed* since the current > behaviour suits the customers Red Hat services and Red Hat > themselves are the effective maintainers of glibc. Reading some glibc mailing list (libc-alpha) posts last year, I remember excessive RSS usage is one of the areas they're tackling due to user complaints. Heck, I even seem to even recall a half-hearted proposal a few years ago to use jemalloc in glibc. I should also note the newish glibc 2.26 has the thread-caching malloc as a build-time option, so it should reduce contention on arenas and allow using fewer arenas. We also have regular contributions from Red Hat employees to Ruby, so I think RH does care about Ruby to some degree; and I don't think the allocation patterns for Ruby would be too different from a lot of existing software. (I have no affiliation with Red Hat, past or present)