public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Eric Wong <e@80x24.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [RFT] malloc: reduce largebin granularity to reduce fragmentation
Date: Mon, 27 May 2024 15:06:02 +0200	[thread overview]
Message-ID: <87r0dnz9ol.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20240409093352.M757838@dcvr> (Eric Wong's message of "Tue, 9 Apr 2024 09:33:52 +0000")

* Eric Wong:

> Anybody volunteers to help test and get reproducible results for
> this?  Thanks in advance.
>
> Testing and getting reproducible results is proving extremely
> expensive due to trace sizes and CPU usage required to handle
> my existing web/IMAP/NNTP-facing traffic.
>
> But the theory works in my mind and could be a solution to a
> problem I've noticed for decades at this point across long-lived
> Ruby and Perl web daemons.
>
> I'm also considering having this as a tunable and mallopt(3).
>
> And perhaps limiting the alignment to pagesize can work, because
> 20% of a large sliding mmap_threshold on 64-bit is several
> megabytes...

I looked at the patch and you did not eliminate the mostly-unused bins.
(They can still get used due to fragmentation.)  So you get a strange
conflation of various effects with this patch.  If we're serious about
this, we need to test something that reduces the bin count.  I'm not
sure if it makes senst to test this current version.

Thanks,
Florian


  reply	other threads:[~2024-05-27 13:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09  9:33 Eric Wong
2024-05-27 13:06 ` Florian Weimer [this message]
2024-04-12 15:19 Wilco Dijkstra
2024-04-12 15:35 ` Cristian Rodríguez
2024-04-12 17:02 ` Eric Wong
     [not found] <CAPBLoAfHRKGRjFQFKHXwK6vX7xxUqkoj?= =?ISO-8859-1?Q?-=5Fsttmfn4FgiEgondA@mail.gmail.com>
2024-04-12 21:50 ` DJ Delorie

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=87r0dnz9ol.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=e@80x24.org \
    --cc=libc-alpha@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: link
Be 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).