On Tue, Aug 01, 2006 at 03:52:05AM +0200, tbp wrote: > As i don't know which party (g++, stdc++, cygwin) to put the blame on > i'll start here. > I've traced back a weird performance issue to a 'new' returning non > cpu-local memory but only when the binary is launched from the > shell/console. That suggests some crt friction. > (threads where those allocations happen are properly binded to one cpu)
Since this seems to have to do with the runtime, I think you need to talk to the Cygwin folks.
