From: Lee <ler762@gmail.com>
To: cygwin@cygwin.com
Subject: Re: calloc speed difference
Date: Sat, 13 Jan 2018 10:04:00 -0000 [thread overview]
Message-ID: <CAD8GWss8tFHF7NB+XBJ0Sqa8A=CJRx2=wsuj4H=7ZeJ-pwD6JA@mail.gmail.com> (raw)
In-Reply-To: <20180112143339.GE24623@calimero.vinschen.de>
On 1/12/18, Corinna Vinschen wrote:
> On Jan 12 15:06, Christian Franke wrote:
>> Lee wrote:
>> > Why is the cygwin gcc calloc so much slower than the
>> > i686-w64-mingw32-gcc calloc?
>> > 1:12 vs 0:11
<.. snip example prog ..>
>>
>> Could reproduce the difference on an older i7-2600K machine:
>>
>> Cygwin: ~20s
>> MinGW: ~4s
<.. snip possible explanation ..>
>
> But then again, Cygwin's malloc *is* slow, particulary in
> memory-demanding multi-threaded scenarios since that serializes all
> malloc/free calls.
>
> The memory handling within Cygwin is tricky. Attempts to replace good
> old dlmalloc with a fresher jemalloc or ptmalloc failed, but that only
> means the developer (i.e., me, in case of ptmalloc) was too lazy...
> busy! I mean busy... to pull this through.
>
> Having said that, if somebody would like to take a stab at replacing
> dlmalloc with something leaner, I would be very happy and assist as
> much as I can.
I just took a quick look at some malloc code & docs and I know enough
to know that I'm not going to be the one taking a stab at replacing
dlmalloc. Sorry :(
Lee
--
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:[~2018-01-13 10:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 7:19 Lee
2018-01-12 8:38 ` Eliot Moss
2018-01-12 9:07 ` Marco Atzeri
2018-01-12 10:52 ` Lee
2018-01-21 11:01 ` Marco Atzeri
2018-01-12 14:05 ` Christian Franke
2018-01-12 14:33 ` Corinna Vinschen
2018-01-12 19:59 ` cyg Simple
2018-01-12 20:07 ` cyg Simple
2018-01-12 20:41 ` Corinna Vinschen
2018-01-12 22:34 ` cyg Simple
2018-01-13 10:48 ` Lee
2018-01-13 10:04 ` Lee [this message]
2018-01-12 22:00 ` Eliot Moss
2018-01-13 8:35 ` Lee
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='CAD8GWss8tFHF7NB+XBJ0Sqa8A=CJRx2=wsuj4H=7ZeJ-pwD6JA@mail.gmail.com' \
--to=ler762@gmail.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).