public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "safinaskar at mail dot ru" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug malloc/30852] Big deallocation takes 8 minutes Date: Fri, 15 Sep 2023 13:02:26 +0000 [thread overview] Message-ID: <bug-30852-131-XkO6mfFseJ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30852-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30852 --- Comment #2 from Askar Safin <safinaskar at mail dot ru> --- Thanks for investigation! > from the swap used value it *does* seem that you are stressing it instead of the allocator Yes, exactly! Program's occupied memory doesn't fit in physical memory. And I don't like that in such situation deallocation takes very long time. My actual production program is written in Rust. In Rust deallocation happens automatically. This means that I have to insert ugly "_Exit(0)" call before the end of program to prevent deallocation to make the program faster. The need for such ugly hacks means that something gone wrong > does it use compression or encryption? No > the IO bandwidth, the media throughput Swap is located on NVMe SSD device (in my laptop) > the system load I had a lot of apps opened in that time -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-09-15 13:02 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-14 14:50 [Bug malloc/30852] New: " safinaskar at mail dot ru 2023-09-14 17:18 ` [Bug malloc/30852] " adhemerval.zanella at linaro dot org 2023-09-15 13:02 ` safinaskar at mail dot ru [this message] 2023-09-15 13:18 ` adhemerval.zanella at linaro dot org 2023-09-15 18:00 ` safinaskar at mail dot ru
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-30852-131-XkO6mfFseJ@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).