First time you hit your application your application is compiled and
Application_Init runs..
So depends on how big it is and how time consuming your Application_Init is
the delay is expected.
Also after some period of inactivity your application is unloaded. Hence if
will be recompiled and Init run again next time you hit it.
To speed things up you can do following....
1. Precompiled it. (if you using .NET 2.0) Google it up how to do it.
2. Disable unloading.... You need to have access to IIS management console
and go into the Pools under "IIS" tree.. There will be an option there...
George.
"Wannabe" <Wa*****@discussions.microsoft.comwrote in message
news:81**********************************@microsof t.com...
>I have a page that take 10-15 seconds to load up the first time you access
it. Once the page loads, it runs super quick, but that initial hit (like
after an hour if no one has hit the page) takes a long time to come up.
Just to rule out databases, and any other external thing I could think of,
I
tried creating a website that had nothing but one page. On that page, I
put a
label that displayed the time when accessed. This page did exactly the
same
thing as above.
Anyone got any suggestions on what I can try?