From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: [RFC] daemon: experimental PREALLOC_NR env knob
Date: Thu, 14 Mar 2024 19:36:53 +0000 [thread overview]
Message-ID: <20240314193653.M993823@dcvr> (raw)
In-Reply-To: <20240224085250.3632004-1-e@80x24.org>
Abandoning this idea for now...
jemalloc via LD_PRELOAD seems be working out to deal with
fragmentation. I hope to be able to steal jemalloc ideas for
glibc malloc to give a better out-of-the-box experience on
GNU/Linux systems.
prev parent reply other threads:[~2024-03-14 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 8:52 [RFC] daemon: experimental PREALLOC_NR env knob Eric Wong
2024-03-14 19:36 ` Eric Wong [this message]
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240314193653.M993823@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.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).