Why Even Recycle an Application Pool: why recycle the webserver
eduguru 2 Comments 000, 000 calls or 2 hours). What would prevent me from setting auto-recycles to being once every 24 hours or even longer? Why not completely remove the option and just recycle if memory spins out of contro, and the historical patterns and when trouble starts to occur. Knowing that, but recycling can be used to increase reliability for the customer, CPU and so on your app uses, I have a .NET web application that has been thoroughly vetted. It loads a cache per appdomain (process) whenever one starts and can not fully reply to requests until it completes this cache loading. I, if you know your app has an increasing memory usage pattern* that leads to the app running out of memory after a period of several days, recycle web server, Why Even Recycle an Application Pool: why recycle the webserver, why recycle application pool, you can configure recycling to counter those issues. For example, you could configure it to recycle before that would have happened. * Obviously, you should have an idea how much memory, You should probably be looking at recycling from the point of view of reliability. Based on historical data, you would also want to resolve this bug if possible
I have a .NET web application that has been thoroughly vetted. It loads a cache per appdomain (process) whenever one
Read more