Maximize IIS application pool availability
with application initialization.
A week ago, I blogged about our first IIS expert guide on restarting IIS websites. Since then, we’ve released part 2 of this series, which I am very excited about:
This really should have been called “How to make sure my IIS site stays up and at peak performance always, even if I recycle it”.
We combine all the pieces of the puzzle with application initialization, always running apppools, and optimal recycling strategies into one prescription that basically makes your site unstoppable (in a good way):
- It always comes up WARM (so your users don’t experience the poor performance due to loss of cache)
- It recycles with zero startup delay (even though you are doing warmup)
I make this point in the guide, but if you think about it, normally these things would be in complete opposition. Either you are warming up the app and then you have a startup delay, or you start fast but experience cold performance.
In the guide, we’ll show you how to get both. Seriously.
And with zero code changes.
I am not sure if you are getting this, but I am very excited about this one. Head over to the IIS apppool warmup guide for the details.