Hi, On 9. Jul 2014, at 23:30, cpapado <[email protected]> wrote:
> Stefan, the profiling numbers that I reported in the first post were > actually from one of the moments during which the application "stalled". It > is actually pretty interesting, the CPU utilization graph from the profiling > showed spikes at similar intervals to the stalls so I just grabbed some > statistics from one of those "spike" time intervals and reported them :). That's good information. Can you do a bit more drill-down on this trace? I see two options: 1) There is some regular expensive call, e.g., BufferCache::compact, being run 2) For some reason there is a spike in co::Commands, e.g., caused by an "event storm" > I'll give a shot at compiling the version of Collage that Carsten just > pointed too and let you guys know how it goes. Stefan, I'm also noticing > that in the Issue #38 link you mention something about paying attention to > > 64 connection threads in windows? What does that pertain to? WaitForMultipleObjectsEx takes at most 64 handles. Once ConnectionSet reaches this limit, it delegates up to 63 Connections to a sub-ConnectionSet in a thread and adds one handle for the thread to the master set. You'll find this in the code easily, but it obviously complicates the implementation of #38. HTH, Stefan.
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ eq-dev mailing list [email protected] http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev http://www.equalizergraphics.com
