Many administrators, especially those who do virtual hosts may have encountered IIS cpu100%, but do not know which site resources occupy more, the following describes a method to view the resource usage of each Web site
This method is not recommended for use at ordinary times, but only when problems arise.
1, set each site as an independent process
Open the IIS Site Properties--Home directory--application protection is changed to high
Open Task Manager to view the process you'll see a few more Dllhost.exe processes and their resource usage these are the processes for each Web point, but now it's not known which Web site uses that process
2, the Dllhost.exe process of the corresponding web site
Open Build Management---Component Services--computer--My computer--COM + applications
Here we can see something like iis-{domain.com//root} that is not visible as a standalone process, this is the Web site in IIS, select the Status View on the toolbar
You're going to see something like this.
Name Run PID
Iis-{down.789game.com//root} is 1688
PID is the Dllhost.exe PID value in task management.
Okay, now that you know the Dllhost.exe process that each Web site uses, and you know Dllhost.exe's resources in the Task Manager, you should know that the site is not working properly.