An ASP.NET web app running on IIS6 periodically shoots the CPU up to 100%. It\'s the W3WP that\'s responsible for nearly all CPU usage during these episodes. The CPU stays pinne
This is a very old post, I know, but this is also a common problem. All of the suggested methods are very nice but they will always point to a process, and there are many chances that we already know that our site is making problems, but we just want to know what specific page is spending too much time in processing. The most precise and simple tool in my opinion is IIS itself.