title: Why Even Recycle an Application Pool?
body: <p>Maybe someone can shed some light on this simple question:</p>
  
  <p>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.</p>
  
  <p>I have been examining the settings on my application pools and have started wondering why I was even recycling so often (once every 1,000,000 calls or 2 hours).</p>
  
  <p>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 control for the appdomain?</p>