I know this fits in MS Development but it affects my hosting as a reseller so I thought I would start here.
I just got a response to a ticket about Jodohost recycling IIS on win5 every 4 hours because of resource consumption due to ASP.NET. Just wondering if this is correct or do you mean the asp.net worker process. If you are restarting IIS just because of ASP.Net you could set the Memory limit lower and let the worker process restart itself, which actually starts a new process and hands off the currently running process so you really never have down time. This would keep from taking down none asp.net sites. That's what we do at the office. Just a thought and you probably have already come across this.
Here is an article about that
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/DBGch01.asp
and
http://www.microsoft.com/resources/...2003/all/deployguide/en-us/iisdg_upg_exzn.asp
I just got a response to a ticket about Jodohost recycling IIS on win5 every 4 hours because of resource consumption due to ASP.NET. Just wondering if this is correct or do you mean the asp.net worker process. If you are restarting IIS just because of ASP.Net you could set the Memory limit lower and let the worker process restart itself, which actually starts a new process and hands off the currently running process so you really never have down time. This would keep from taking down none asp.net sites. That's what we do at the office. Just a thought and you probably have already come across this.
Here is an article about that
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/DBGch01.asp
and
http://www.microsoft.com/resources/...2003/all/deployguide/en-us/iisdg_upg_exzn.asp