StephenC wrote:I'm really surprised that the profiler is having anywhere near that sort of impact. With the low impact mode I've never seen it have any sort of signicicant impact.
Did enabling inlining make any difference?
AndrewH wrote:That certainly does sound like an unusually high amount of overhead.
Are you using a virtualized environment? Some VM implementations don't provide a very efficient way of reading the CPU time stamp counter which can have a negative effect on the performance of the profiler. A warning is written to the log file if this is detected.
On XP you should be able to find this in ...
Also, are you using .NET 1.1? The profiler API available in that version of .NET is much less efficient than the one introduced into .NET 2.0. For many applications you can work around this by forcing them to run using the .NET 2.0 framework while profiling using an application config file.
Users browsing this forum: No registered users and 0 guests