title: Dangers of lengthening IIS app pool recycle interval
body: <p>I have a .NET application running in IIS7 that has a very large connected service attached to it. Because it is so large, the site takes a very long time (10-15 minutes) to "spool up" again after the app pool is recycled (it's currently set to the default recycle interval of every 29 hours or something). My problem is that in the environment I'm working in, having an application that takes that long to start every morning isn't acceptable. So my question is, what are the dangers of setting the app pool to recycle less frequently? Say once a week or even once a month? The application will be running on its own pool, so other applications don't need to be taken into account. Thanks!</p>