Thank you again for the response Stefan. Drilling all the way down the traces, I'm noticing that the majority of CPU time is spent in NtDeviceIoControFile (~23%) and NtWaitForMultipleObjects (~14%). All the calls to NtDeviceIoControlFile stem from co::SocketConnection::write(). The calls to NtWaitForMultipleObjects all stem from co::ConnectionSet::select(). I'm not seeing anything else in the trace that would indicate an expensive out-of-place Collage call happening fairly regularly. I can also upload one of the Visual studio profiler traces if you want to take a closer look.
Is there a way to aggregate and dump Collage statistics to a file? Maybe that will provide some more insight. I also checked whether our software was accidentally pulling in some debug-mode DLLs but that was not the case. Finally, I tried the Collage edits that Carsten suggested by cherry-picking the relevant commits on top of the Collage version that we use (1.1.0) but I guess I messed something up because it would infinite loop during initialization (and yes, I did recompile EQ and our software against it as well). Thanks again :) -Harris -- View this message in context: http://software.1713.n2.nabble.com/Jittery-performance-with-large-cluster-tp7585928p7585960.html Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com. _______________________________________________ eq-dev mailing list [email protected] http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev http://www.equalizergraphics.com
