Breaking apart IISRESET,
IIS pool recycling, and website restarts.
When I picked restarting IIS as the topic to dig into first, I thought this was kind of a random place to begin. Especially given how many other, seemingly more exciting things I will be talking about, including hangs, scalability, session state, async, and all the others.
(To skip my rambling and go straight to the guide, head to How to correctly reset, restart, and recycle IIS websites.)
But after thinking more about it, I decided it was a perfect place to begin. Recycling and restarting your IIS website in production is something everyone running IIS deals with regularly … no matter what kind of app you have. And it’s the first thought that goes through your mind when your website is running poorly.
Plus, turn out there is A LOT of improvements that can be created here, and most without any code changes to your applications.
Reset, restart, and recycle IIS the right way
I based this guide on our experience with LeanSentry customers recycling their production sites … or being afraid of production recycling. We drew on our best practices on when and how to best restart their sites for different kinds of problems.
Then, we also did some extensive testing to help configure IIS sites to become recycle resilient.
The result is a 5+ guide series that explores:
- How and WHEN to restart IIS websites in production, for best results.
- Plus the costs of application pool recycling, and how to manage them.
- The dangers of IISRESET …
- Plus downtime impact of every possible way to reset and recycle IIS.
- A guide on configuring your IIS site for maximum warmup, with zero downtime, zero startup delay, 100% warm operation. Even if you recycle!
- Plus a tool to configure your site to do this …
- and to test your warmup performance.
- A developer guide on how to speed up production warmup, using several battle-tested code techniques we use.
Guide newsletter and Early access
I am very interested in getting community feedback on this content. So, we’ll be releasing the guides through our Guide newsletter and giving people a chance to comment/ask questions.
I’ll be doing my best to incorporate requests and answer questions.
So, if you use IIS or build IIS and ASP.NET websites, and you feel that this content is useful, you can have a lot of input into what we cover. If you want early access to the guides and tools that will come out publicly later, be sure to hit “early access”.
I hope you find these useful, and I’ll see you in the guides.