Via the IIS management console, you can view the running worker processes.

There’s a chance that you could recognize one of the URLs that’s known to take a very long time or cause high CPU issues.Īlthough, this may also show a bunch of web requests that are queued up and not directly lead you to the root cause. This may help you identify a specific URL that is causing the problem. One of the first things you should do is see which web requests are currently executing. To start, you should look at which web requests are currently executing with IIS to see if that helps you identify the issue to be able to troubleshoot IIS worker process. We’ll cover some of the top reasons and how to troubleshoot IIS performance problems. There are a lot of reasons that your IIS worker process ( w3wp.exe) could be using a lot of CPU. In this post, we’ll discuss some tips to identify what’s causing high CPU usage for your ASP.NET web applications. Having IIS performance problems? Do you have w3wp.exe high CPU usage? How do you troubleshoot IIS Worker Process High CPU usage?

Monitor cpu usage windows 10