From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by sourceware.org (Postfix) with ESMTP id A67243857C53 for ; Mon, 21 Sep 2020 08:52:21 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org A67243857C53 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-438-UZYkA4iaPf2w67uoXD-irQ-1; Mon, 21 Sep 2020 04:52:17 -0400 X-MC-Unique: UZYkA4iaPf2w67uoXD-irQ-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 760281007461; Mon, 21 Sep 2020 08:52:16 +0000 (UTC) Received: from oldenburg2.str.redhat.com (ovpn-114-108.ams2.redhat.com [10.36.114.108]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C603A60C13; Mon, 21 Sep 2020 08:52:15 +0000 (UTC) From: Florian Weimer To: Xavier Roche via Libc-help Cc: Xavier Roche Subject: Re: Abnormal memory usage with glibc 2.31 related to trimming strategy ? References: <71a1cf97a5a9801a2aaf146e5584b63add4dcd2e.camel@yandex.ru> Date: Mon, 21 Sep 2020 10:52:14 +0200 In-Reply-To: (Xavier Roche via Libc-help's message of "Mon, 21 Sep 2020 10:39:04 +0200") Message-ID: <87y2l37br5.fsf@oldenburg2.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-7.2 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H5, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-help@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-help mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2020 08:52:22 -0000 * Xavier Roche via Libc-help: > Just a note: this is unfortunately not related to the number of heaps. > While 2.31 has more heaps than 2.23 in our setup (96 heaps in 2.31 vs. > 57 heaps in 2.23), reducing the number of heaps to the number of cores > (ie. 12 heaps, as suggested on a developper's blog: > https://codearcana.com/posts/2016/07/11/arena-leak-in-glibc.html) does > not appear to reduce the wasted space, with a steady rate of 10GB/hour > space lost. Then this looks like a distinct issue. Do you use any of the memalign functions or C++'s aligned new operator? Thanks, Florian -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill