By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
457,728 Members | 1,154 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 457,728 IT Pros & Developers. It's quick & easy.

Application Start Delay

P: n/a
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!
Nov 19 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
The delay is because of asp.net restarting. Other then changing how often it
might need to restart in machine.config, there is not much you can do.

And yes, this is very annoying during development. After every recompile, it
takes forever for it to start up again (lot's of DLLs that are part of the
app).

"Jeremy S" <A@B.COM> wrote in message
news:O1**************@TK2MSFTNGP14.phx.gbl...
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!

Nov 19 '05 #2

P: n/a
The shutting down of the worker processes after 20 mins is probably the cause.
I had this too and disabled and it ran fine.

Let me know if you have any more questions..

Cheers,
Tom Pester
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!

Nov 19 '05 #3

P: n/a
What do you mean you disabled it? Did you simply extend the idle timeout
value - or did you do something else?

<To********************@pandora.be> wrote in message
news:a1**************************@news.microsoft.c om...
The shutting down of the worker processes after 20 mins is probably the
cause. I had this too and disabled and it ran fine.

Let me know if you have any more questions..

Cheers,
Tom Pester
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!


Nov 19 '05 #4

P: n/a
I thought I disabled it but its a long time ago.

Cheers,
Tom Pester
What do you mean you disabled it? Did you simply extend the idle
timeout value - or did you do something else?

<To********************@pandora.be> wrote in message
news:a1**************************@news.microsoft.c om...
The shutting down of the worker processes after 20 mins is probably
the cause. I had this too and disabled and it ran fine.

Let me know if you have any more questions..

Cheers,
Tom Pester
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!

Nov 19 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.