From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 493E33858CDA; Thu, 14 Sep 2023 17:18:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 493E33858CDA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1694711887; bh=htNlYyysvnC82jlULLWEfSx9+6ce4++rQDmkxieAYaQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=AwbgVfXvaNIFabhtQ2NHdNHFErzehB+yvCFfGwDqRBWuVSzTEsjuXsOf9BXTDpnbf 6hj3yYmbY2OAVfqqbo5fH//ouxJ9Zne9MK2i/BwAjLyzdeu65QyVizd8k9XqsLpSjQ wGNIeGqRYJnJPSPAIQzma0po4THgAqQ8O1vmg1U8= From: "adhemerval.zanella at linaro dot org" To: glibc-bugs@sourceware.org Subject: [Bug malloc/30852] Big deallocation takes 8 minutes Date: Thu, 14 Sep 2023 17:18:06 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: malloc X-Bugzilla-Version: 2.37 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: adhemerval.zanella at linaro dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30852 Adhemerval Zanella changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adhemerval.zanella at lina= ro dot o | |rg --- Comment #1 from Adhemerval Zanella --- This testcase roughly allocates about ~38GB and from the swap used value it *does* seem that you are stressing it instead of the allocator. With a testcase adjusted to measure the time directly (instead of calling system) using clock_gettime on a machine with enough memory (so swap is not used): glibc 2.37: allocation: 15.267103395 seconds free: 5.583120996 seconds glibc 2.38: allocation: 15.316940207 seconds free: 5.149215347 seconds master: allocation: 15.840980439 seconds free: 5.157396663 seconds Could you check with perf if the swap utilization is indeed the case? If it were the case, there is not much glibc or any allocator can do. I would dep= end heavily of how swap was configured (does it use compression or encryption?), the IO bandwidth, the media throughput, the system load, etc. --=20 You are receiving this mail because: You are on the CC list for the bug.=