IIS’s Overlapping App Pools-Week 16

Microsoft’s Internet Information Services (IIS) web platform is extremely robust, and one of the neat features is overlapping application pools.

In today’s video I cover the theory behind overlapping app pools, forcibly killing the w3wp.exe worker process and on-demand starting of app pools.  This is helpful in knowing the impact of recycling an application pool, and what measures you can take when troubleshooting high CPU, high memory or other issues in your IIS environment.

This is week 16 of a 52 week series on various web administration related tasks. Past and future videos can be found here.

Having problems viewing on your mobile device?  Click here instead.


  • At the end you mention that recycling the app pool through the IIS management interface would only affect one node (assuming multiple nodes and shared storage/configuration). However, touching the web.config on shared storage would necessarily trigger a reset of all the app pools on all nodes using shared storage/configuration wouldn't it?

  • Hi Jeffrey,

    Yes, good point. You're correct, that will cause an appdomain recycle on all nodes since File Change Notification (FCN) will notice the change on all nodes. Week 12 I talked about AppDomains, which covered part of this, with examples. http://weblogs.asp.net/owscott/archive/2011/03/19/asp-net-appdomain-what-it-is-and-why-it-s-important-part-12-of-52-part-series.aspx

Comments have been disabled for this content.