From: "John Hein" <3fbmqnhaz4@snkmail.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin multithreading performance
Date: Mon, 23 Nov 2015 10:27:00 -0000 [thread overview]
Message-ID: <24780-1448274431-7444@sneakemail.com> (raw)
In-Reply-To: <5652C402.7040006@maxrnd.com>
Mark Geisert wrote at 23:45 -0800 on Nov 22, 2015:
> Corinna Vinschen wrote:
> > On Nov 21 01:21, Mark Geisert wrote:
> [...] so I wonder if there's
> >> some unintentional serialization going on somewhere, but I don't know yet
> >> how I could verify that theory.
> >
> > If I'm allowed to make an educated guess, the big serializer in Cygwin
> > are probably the calls to malloc, calloc, realloc, free. We desperately
> > need a new malloc implementation better suited to multi-threading.
>
> That's very helpful to know. I'd want to first make sure the heavy lock
> activity I'm seeing in the traces really is due to malloc() and friends
> but I couldn't help a speculative search online for multithread-safe
> malloc(). These turned up:
> tcmalloc - part of google-perftools, requires libunwind, evidently
> not yet ported to Windows AFAICT,
> nedmalloc - http://www.nedprod.com/programs/portable/nedmalloc/
> ptmalloc - http://www.malloc.de/
>
> The latter two are based on Doug Lea's dlmalloc which is also the basis
> of Cygwin's malloc() functions. As I understand it, ptmalloc in one
> form or another has been part of glibc on Linux for some time.
>
> So there may be a solution in sight if we need to go that direction. Of
> course, SHTDI as usual :).
>
> ...mark
Someone recently mentioned on this list they were working on porting
jemalloc. That would be a good choice.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-11-23 10:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 0:24 Kacper Michajlow
2015-11-19 20:24 ` Mark Geisert
2015-11-20 14:25 ` Kacper Michajlow
2015-11-21 9:21 ` Mark Geisert
2015-11-21 10:53 ` Corinna Vinschen
2015-11-23 7:45 ` Mark Geisert
2015-11-23 10:27 ` John Hein [this message]
2015-11-24 1:05 ` Mark Geisert
2015-11-26 9:49 ` Corinna Vinschen
2015-11-26 10:49 ` Mark Geisert
2015-12-05 10:51 ` Mark Geisert
2015-12-05 13:07 ` Kacper Michajlow
2015-12-05 13:59 ` Kacper Michajlow
2015-12-05 22:40 ` Mark Geisert
2015-12-06 2:35 ` Kacper Michajlow
2015-12-06 8:02 ` Mark Geisert
2015-12-06 20:56 ` Kacper Michajlow
2015-12-08 10:51 ` Mark Geisert
2015-12-08 15:34 ` Corinna Vinschen
2015-12-08 17:02 ` Corinna Vinschen
2015-12-18 15:06 ` Achim Gratz
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=24780-1448274431-7444@sneakemail.com \
--to=3fbmqnhaz4@snkmail.com \
--cc=cygwin@cygwin.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).