Knowing and using .NET memory and performance profilers (like e.g. RedGate's ANTS Profiler) very well in my development environment, I still found no real way to do it on a production server.
Currently I'm experiencing every now and then 100% CPU usage of w3wp.exe for a certain application pool.
Looking at various performance counters, I'm still unable to determine the real cause, since I cannot determine in which part of my code the high CPU utilization takes place.
I've tried CLR Profiler on the live server (with no meaningful result) and I even could imagine installing ANTS Profiler and let it run for hours to get some measurement logs.
Just to be sure I'm doing it right, my question is:
What is the best way to do some ad hoc measurements on a production IIS 7 web server to detect code bottlenecks?