In IIS6, w3wp memory usage often fails to be released in time, resulting in slow server response.
After studying it today, you can make the following configurations:
1. Separate applications for each website in IISProgramPool configuration. That is, they do not affect each other.
2. Set the recycle time of the application pool. The default value is 1720 hours, which can be modified as needed. At the same time, set the number of w3wp processes that run simultaneously to 1. Then, when the memory or CPU usage exceeds the limit, the memory will be automatically reclaimed.
In general, this can be solved. However, some websites cannot be correctly released due to program problems.
So how can we find the website?
1. Add the PID field to the task manager. You can see the process PID with the highest memory usage or CPU usage.
2. Run iisapp-A at the command prompt. Note: the first running will prompt that no JS support is available. Click OK. Then run it again. In this way, we can see the application pool corresponding to the PID.
3. Check the website corresponding to the application pool in IIS.