From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Mark Geisert <mark@maxrnd.com>
Cc: cygwin-developers@cygwin.com
Subject: Re: Cygwin malloc tune-up status
Date: Sun, 27 Sep 2020 18:54:36 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2009271852490.50@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <067987e2-e958-b56c-efea-25d827568453@maxrnd.com>
Hi Mark,
On Thu, 24 Sep 2020, Mark Geisert wrote:
> I've been looking into two potential enhancements of Cygwin's malloc operation
> for Cygwin 3.2. The first is to replace the existing function-level locking
> with something more fine-grained to help threaded processes; the second is to
> implement thread-specific memory pools with the aim of lessening lock activity
> even further.
>
> Although I've investigated several alternative malloc packages, including
> ptmalloc[23], nedalloc, and Windows Heaps, only the latter seems to improve on
> the performance of Cygwin's malloc. Unfortunately using Windows Heaps would
> require fiddling with undocumented heap structures to enable use with fork().
> I also looked at BSD's jemalloc and Google's tcmalloc. Those two require much
> more work to port to Cygwin so I've back-burnered them for the time being.
I am just a lurker when it comes to your project, but I wonder whether you
had any chance to look into mimalloc
(https://github.com/microsoft/mimalloc)? I had investigated it in Git for
Windows' context for a while (because nedmalloc, which is used by Git for
Windows, is no longer actively maintained).
Ciao,
Dscho
next prev parent reply other threads:[~2020-09-28 13:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 6:01 Mark Geisert
2020-09-27 16:54 ` Johannes Schindelin [this message]
2020-09-29 2:22 ` Mark Geisert
2021-04-01 9:19 ` Teemu Nätkinniemi
2021-04-02 5:45 ` Maybe consider rpmalloc -- Was: " Mark Geisert
2021-04-03 2:53 ` Maybe consider rpmalloc Mark Geisert
2021-04-03 6:46 ` Teemu Nätkinniemi
2021-04-03 6:48 ` Teemu Nätkinniemi
2021-04-11 9:28 ` Mark Geisert
2021-04-12 8:48 ` Teemu Nätkinniemi
2021-04-13 8:24 ` Mark Geisert
2021-04-13 13:05 ` Teemu Nätkinniemi
2021-04-14 8:19 ` Mark Geisert
2021-04-14 18:36 ` Teemu Nätkinniemi
2021-04-14 18:53 ` Jon Turney
2021-04-19 5:16 ` Mark Geisert
2021-04-20 19:34 ` Jon Turney
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=nycvar.QRO.7.76.6.2009271852490.50@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=cygwin-developers@cygwin.com \
--cc=mark@maxrnd.com \
/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).