From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin multithreading performance
Date: Thu, 26 Nov 2015 10:49:00 -0000 [thread overview]
Message-ID: <5656DDEF.9070603@maxrnd.com> (raw)
In-Reply-To: <20151126093427.GJ2755@calimero.vinschen.de>
Corinna Vinschen wrote:
> On Nov 23 16:54, Mark Geisert wrote:
>> John Hein wrote:
>>> 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.
[...]
>>>
>>> Someone recently mentioned on this list they were working on porting
>>> jemalloc. That would be a good choice.
>>
>> Indeed; thanks for the reminder. Somehow I hadn't followed that thread.
>
> Indeed^2. Did you look into the locking any further to see if there's
> more than one culprit? I guess we've a rather long way to a "lock-less
> kernel"...
It took me a while to figure out what I wanted to see in the strace
logs. I ended up adding a small patch to pthread_mutex::lock() to
record a timestamp on entry, and also log that in the pthread_printf()
near the end of the method. With that I'm able to see how long a thread
has to wait for a lock before actually acquiring it. That will allow me
to unravel the sequence of locking and unlocking and give stats for all
threads and/or locks. That could be generally useful to evaluate
different memory allocators or different locking strategies using the
same allocator.
But that is just groundwork to identifying which locks are suffering the
most contention. To identify them at source level I think I'll also
need to record the caller's RIP when they are being locked.
In the raw strace data I'm looking at for the OP's testcase, I can see a
lot of cases where a thread wants a lock but is delayed for milliseconds
before getting ahold of it. I can't say ATM whether it's just one or a
few locks suffering this way, or more. Work continues :).
..mark
--
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-26 10:24 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
2015-11-24 1:05 ` Mark Geisert
2015-11-26 9:49 ` Corinna Vinschen
2015-11-26 10:49 ` Mark Geisert [this message]
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=5656DDEF.9070603@maxrnd.com \
--to=mark@maxrnd.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).