Application Pool recycling introduces no network downtime and should happen
pretty fast. The actual time depends on your application characteristics.
There are timers which monitor how long a process takes to
shutdown/startup/recycle (90 seconds by default), which prevents stragglers
from hanging out.
What happens is that simultaneously, the old worker process stops picking up
requests (it just tries to finish existing request process) while the new
worker process picks up all subsequent requests. Thus, you should see no
downtime at all since all requests get processed and no connections get
dropped.
Application Pool recycling does destroy in-process state, like session state
for ASP. ASP.Net has a dedicated-process session state service which works
regardless of recycling.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Andy Cheung" <andycheung2000.DeleteThis@hotmail.com> wrote in message
news:f007cbe5.0406170501.169ebd4e@posting.google.com...
I'd like to set my worker processes to recycle at 3am every day. My
question - how long does it take to recycle? Will my web server be
unavailable during the time it tkaes to recycle?
>> Stay informed about: IIS 6.0 Worker Processes - impact to server during recycle?