Under IIS6, often w3wp memory footprint can not be released in time, causing the server to respond slowly.
Today, a little research, you can do the following configuration:
1, a separate application pool configured for each site in IIS. That does not affect each other.
2, the recovery time is provided in the application pool, the default is 1720 hours, it can be modified according to the situation. At the same time, the number of w3wp processes running simultaneously set to 1. Then set when the memory or cpu usage much more than, it automatically reclaims memory (Note: virtual memory is based refers to the number of virtual memory for the entire system with virtual memory, and second, not iis occupied, such as set to 1G, then the system memory usage as long as more than 1G, IIS process will reclaim its own memory)
In general, this can be resolved. But there will still be individual sites because of procedural issues, not properly released.
So, how to find which one site?
1, increase the display pid field in the Task Manager. You can see the take up memory or the highest pid process of the CPU
2, run iisapp -a at the command prompt. Note that the first time you run, you will be prompted no js support, click OK. Then run it again. So you can see the corresponding application pool pid
3, to which iis look at the corresponding site application pool, on the ok
Today, a little research, you can do the following configuration:
1, a separate application pool configured for each site in IIS. That does not affect each other.
2, the recovery time is provided in the application pool, the default is 1720 hours, it can be modified according to the situation. At the same time, the number of w3wp processes running simultaneously set to 1. Then set when the memory or cpu usage much more than, it automatically reclaims memory (Note: virtual memory is based refers to the number of virtual memory for the entire system with virtual memory, and second, not iis occupied, such as set to 1G, then the system memory usage as long as more than 1G, IIS process will reclaim its own memory)
In general, this can be resolved. But there will still be individual sites because of procedural issues, not properly released.
So, how to find which one site?
1, increase the display pid field in the Task Manager. You can see the take up memory or the highest pid process of the CPU
2, run iisapp -a at the command prompt. Note that the first time you run, you will be prompted no js support, click OK. Then run it again. So you can see the corresponding application pool pid
3, to which iis look at the corresponding site application pool, on the ok
https://www.cnblogs.com/springwind268/p/4718316.html
Under IIS6, often w3wp memory footprint can not be released in time, causing the server to respond slowly.
Today, a little research, you can do the following configuration:
1, a separate application pool configured for each site in IIS. That does not affect each other.
2, the recovery time is provided in the application pool, the default is 1720 hours, it can be modified according to the situation. At the same time, the number of w3wp processes running simultaneously set to 1. Then set when the memory or cpu usage much more than, it automatically reclaims memory (Note: virtual memory is based refers to the number of virtual memory for the entire system with virtual memory, and second, not iis occupied, such as set to 1G, then the system memory usage as long as more than 1G, IIS process will reclaim its own memory)
In general, this can be resolved. But there will still be individual sites because of procedural issues, not properly released.
So, how to find which one site?
1, increase the display pid field in the Task Manager. You can see the take up memory or the highest pid process of the CPU
2, run iisapp -a at the command prompt. Note that the first time you run, you will be prompted no js support, click OK. Then run it again. So you can see the corresponding application pool pid
3, to which iis look at the corresponding site application pool, on the ok