the company’s recent server total CPU100% occupancy, server configuration for dual core Xeon3.0x2, 2G ECC memory. W3wp.exe is found to occupy a large amount of CPU. for a long time this situation should be the site of the program has a dead loop caused by the problem. Before you find a problem, you can temporarily restrict the use of w3wp process CPU method to ensure that the site can work:
The following is the content of the
in IIS6, often appear w3wp.exe memory and CPU can not be released in time, resulting in slow response server.
1, in IIS for each site for a separate application pool configuration. That does not affect each other.
2, set up the application pool CPU monitoring, no more than 25% (server 4CPU), refresh every minute, more than the limit off.
1, in the task manager to increase the display PID field. You can see the maximum PID of memory or CPU
2, run iisapp -a at the command prompt. Note that for the first time, there will be no JS support, click ok. Then run again. This allows you to see the PID application pool. (iisapp is actually a VBS script, stored in the C:windowssystem32 directory of the full name is iisapp.vbs, if you like me, also banned the Vbs default correlation program, you need to manually select the directory, open mode, and then select "Microsoft (R) Windows Based Script Host", the corresponding relationship PID can be obtained with the application pool).
3, IIS to see the application pool corresponding to the site, on the OK, to make the upper limit of memory or CPU, or to check whether the program has the problem of dead loop.