J
Jeremy S
I have written an ASP.NET application that performs very well. I make heavy
use of the Cache and otherwise minimize the number of round trips to to the
db. I couldn't be happier with the performance - except when the application
first starts. When hitting my Web server over the Internet there is a delay
waiting for the first page. I suspect that the App Pool is starting up as
well as my particular ASP.NET Web application. I should note that while I
have some code that runs during Application_Start, it is minimal does not
explain most of the delay. I have noticed this delay on other ASP.NET Web
sites as well.
What can I do to minimize this delay? It appears that the app pool is set to
timeout after 20 minutes. I suspect that is the issue - but is the only
solution to increase the idle timeout on the App Pool? If so, is it
perfectly acceptable to set the App Pool's idle timeout value to something
like 24 hours? Is there anything else I can look at (beyond my
Application_Start code) that might explain this initial delay?
Thanks!
use of the Cache and otherwise minimize the number of round trips to to the
db. I couldn't be happier with the performance - except when the application
first starts. When hitting my Web server over the Internet there is a delay
waiting for the first page. I suspect that the App Pool is starting up as
well as my particular ASP.NET Web application. I should note that while I
have some code that runs during Application_Start, it is minimal does not
explain most of the delay. I have noticed this delay on other ASP.NET Web
sites as well.
What can I do to minimize this delay? It appears that the app pool is set to
timeout after 20 minutes. I suspect that is the issue - but is the only
solution to increase the idle timeout on the App Pool? If so, is it
perfectly acceptable to set the App Pool's idle timeout value to something
like 24 hours? Is there anything else I can look at (beyond my
Application_Start code) that might explain this initial delay?
Thanks!