Thanks for the reply. We had an issue in dot net 3.5 where our application was approximately 50% slower in 64-bit than 32-bit without profiling and were looking at ways we could isolate the issue. The performance loss appeared in Performance Profiler to be distributed quite evenly across the application i.e. no obvious hotspots appeared in the 64-bit profiler that 32-bit did not have. They might be there hidden somewhere but not sure the best way to drill into that?
When we upgraded the solution to dot net 4 and upgraded our 3rd party controls, the issue seems to have been to a large extent resolved but we were looking for some real metric to determine this.
Even better would be to do a quicker validation check by looking at a comparison using Sampling mode first, then if you think it is needed to delve deeper with the more intrusive/detailed profiling modes.
Thanks... not aware of Sampling mode. I'll have a look.
Also when comparing sessions remember there will be environmental conditions to consider, i.e. the load of the the machine due to other processes.
Don't think this is a factor as this is on a local dev machine with no outside influences. Local databases, no other database related applications loaded and no other major CPU hogging applications running. Possible that our antivirus might be causing some sort of problem.