I have a website with very high traffic that receives good 300+ requests / second ( http://cooltext.com ). Rebooting takes at least 90 seconds. Therefore, every time I send a new assembly, it disappears within a minute or two. Long enough to run my monitoring services.
When I make changes that restart the server, it seems that the reboot stops until all the old requests in the old application pool are completed (some of them are very long). I can restart the process faster by killing the old w3wp.exe instance manually.
Is there a way to force IIS to immediately close all connections and perform a hard restart? Some settings in IIS or asp.net to manage this?
source
share