Re: Cygwin multithreading performance

2015-12-05 11:51 GMT+01:00 Mark Geisert : > Mark Geisert wrote: >> >> 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

Re: Jemalloc under CYGWIN

I'm sorry, I got distracted from this issue and hadn't make any progress. One thing specifically I need to be able to work on this issue is some information describing how to build/test cygwin lib (rather than using it). I couldn't find any information on the website, (or I havn't look deeply

Re: Cygwin multithreading performance

2015-12-05 14:07 GMT+01:00 Kacper Michajlow : > 2015-12-05 11:51 GMT+01:00 Mark Geisert : >> Mark Geisert wrote: >>> >>> Corinna Vinschen wrote: On Nov 23 16:54, Mark Geisert wrote: > > John Hein wrote: >> >> Mark Geisert wrote at

Re: Jemalloc under CYGWIN

Greetings, Yucong Sun! > I'm sorry, I got distracted from this issue and hadn't make any progress. > One thing specifically I need to be able to work on this issue is some > information describing how to build/test cygwin lib (rather than using > it). I couldn't find any information on the

Re: Cygwin multithreading performance

Mark Geisert wrote: 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

Re: Cygwin multithreading performance

Kacper Michajlow wrote: 2015-12-05 11:51 GMT+01:00 Mark Geisert : Mark Geisert wrote: In the OP's very good testcase the most heavily contended locks, by far, are those internal to git's builtin/pack-objects.c. I plan to show actual stats after some more cleanup, but I did

Re: Cygwin multithreading performance

2015-12-05 23:40 GMT+01:00 Mark Geisert : > Kacper Michajlow wrote: >> >> 2015-12-05 11:51 GMT+01:00 Mark Geisert : >>> >>> Mark Geisert wrote: >>> In the OP's very good testcase the most heavily contended locks, by far, >>> are >>> those internal to git's