It seems that "Thread Times" measured by dotTrace, in sampling mode, is impacted if there is a background application running side by side with the profiler. This situation is a bit annoying because I would have expected the Thread Time to reflect closely the actual CPU consumption of the process, with as much independence as possible regarding to other running processes on the machine.
Are there any plans to improve this situation in the upcoming dotTrace 4.0?
Thanks in advance,
Lokad.com sales forecasting