Right now we just use something like this
stopWatch.Start();
try
{
method();
}
finally
That's a cool tool: http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
The stopwatch should measure time spent only in one thread. You would need to run a separate instance on every thread. This would give you probably the closes results to what you want.
Alternatively (preferred option if you want to monitor the whole application, and not just some methods), there are various performance counters you can use out of the box (they are updated by .Net runtime). There is lots of information on the web, you can start with msdn: http://msdn.microsoft.com/en-us/library/w8f5kw2e(VS.71).aspx
I once solved a similar problem by creating a wrapper for StopWatch that had a StopWatch instance marked as ThreadStatic
.
Alternatively there are tools such as Ants Profiler you can purchase to help you.
Hmm, from Jon Skeet's answer to this question:
Timing a line of code accurately in a threaded application, C#
And also this article:
http://lyon-smith.org/blogs/code-o-rama/archive/2007/07/17/timing-code-on-windows-with-the-rdtsc-instruction.aspx
It seems like there's no simple way to do this.