What to do about the slow startup of web services

re: What to do about the slow startup of web services

Josh L — Wed, 02 Apr 2008 21:21:54 GMT

This article doesn't mention it (perhaps it's assumed) but you can pre-compile your asp.net pages by using Web deployment projects and unchecking "Allow this precompiled site to be updatable". More information here:

http://msdn2.microsoft.com/en-us/library/aa479568.aspx

Ngen adds a number of complications, including ensuring that you don't have any base address conflicts - see this article for more information:

http://msdn2.microsoft.com/en-us/magazine/cc163610.aspx

re: What to do about the slow startup of web services

Fredy Feld — Tue, 07 Oct 2008 05:20:41 GMT

I had the same problem. The reason is that the application domain times out every 20 mins if there is no activity, the first request after the timeout can force a recompile and reload of cache. Changing some settings in the machine.config file will solve the problem; unfortunately for me my hosting provider would not allow me to make this change. I found this utility to be useful.

http://www.spikesolutions.net/ViewSolution.aspx?ID=c2b7edc0-5de1-4064-a432-05f6eded3b82

Essentially it "Pings" my home page every few mins so the application domain does not time out. The utility can also be configured to ping more than one page so that auxiliary pages are fast too.

re: What to do about the slow startup of web services

Dan Ribar — Fri, 19 Dec 2008 18:25:56 GMT

I found that when the website [calling the web service] has debug="true" in the web.config, it loads and does the JIT compilation and takes a while on the first load.

Sitching the debug to "False" eliminates the problem. BTW, I also have set the worker processes to NOT restart, but we learned that many moons ago when we were deploying SSRS. It tends to do the same thing on reports starting slowly for the first time.

Dan Ribar