Profiling thread signalling constructs


I've been a satisfied ANTS profiler ( for some time now but have been annoyed at a small thing:

When profiling multi threaded applications (.net 2.0) that use WaitHandle objects to signal between threads (AutoResetEvent, ManualResetEvent) ANTS reports methods like AutoResetEvent.WaitOne as being the slowest line of code. The same goes for methods like Thread.Join.

Now, these lines don't take up any CPU time, but that is the main thing I'm interested in. I know ANTS profiles actual time and am ok with that, but I would really like an option within the profiler to ignore methods like Thread.Join or WaitHandle.WaitOne. Short of displaying actual CPU time this would be a great help in helping me work more efficiently.

Any chance this could be included in an update?


  • Hi,

    We are currently in the planning phase for a new version of ANTS Profiler and allowing for the differences in CPU and Wall clock time to be accounted for is high on our list of priorities so watch this space!


    James Moore
    Head of DBA Tools
    Red Gate Software Ltd
Sign In or Register to comment.