Is it typical for an 2.0 application take 15 - 20 seconds to start up, after
a long period of inactivity? If not, what can I look at to get it to start
quicker, the first time it is used?

"Wannabe" <(E-Mail Removed)> wrote in message
news:C55253EA-4035-4FDA-A905-(E-Mail Removed)...

> Is it typical for an 2.0 application take 15 - 20 seconds to start up,
> after
> a long period of inactivity?

It can be...

When the last remaining session ends, the Application_End event fires and
the web application shuts down to free up its resources on the webserver -
there's a bit more to it than that, but that is essentially what happens...

> If not, what can I look at to get it to start quicker, the first time it
> is used?

http://www.google.co.uk/search?sourc...ion+keep+alive


--
Mark Rae
ASP.NET MVP
http://www.markrae.net

Hello Wannabe,

Do u use precompiled site?! (Aspnet_compiler.exe)

---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo


W> Is it typical for an 2.0 application take 15 - 20 seconds to start
W> up, after a long period of inactivity? If not, what can I look at to
W> get it to start quicker, the first time it is used?
W>

No, we do not. Since you ask, I'm guessing that it would be a good thing.

"Michael Nemtsev [MVP]" wrote:

> Hello Wannabe,
>
> Do u use precompiled site?! (Aspnet_compiler.exe)
>
> ---
> WBR,
> Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour
>
> "The greatest danger for most of us is not that our aim is too high and we
> miss it, but that it is too low and we reach it" (c) Michelangelo
>
>
> W> Is it typical for an 2.0 application take 15 - 20 seconds to start
> W> up, after a long period of inactivity? If not, what can I look at to
> W> get it to start quicker, the first time it is used?
> W>
>
>
>

There are several thing to keep in mind with .NET

1. If application is not used it will be unloaded. You can change this
behavior in you .NET pool configuration. It will be in IIS Management. (PS:
It's not there in Windows XP so do not look, It's in win2003 IIS management
though).

2. By default .NET recycles the application pool every 24 hours. Again, you
can change it in IIS Management console)

3. Precompile your application. That would save compilation time...

George.


"Wannabe" <(E-Mail Removed)> wrote in message
news:16926603-5233-4D0C-A484-(E-Mail Removed)...
> No, we do not. Since you ask, I'm guessing that it would be a good thing.
>
> "Michael Nemtsev [MVP]" wrote:
>
>> Hello Wannabe,
>>
>> Do u use precompiled site?! (Aspnet_compiler.exe)
>>
>> ---
>> WBR,
>> Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour
>>
>> "The greatest danger for most of us is not that our aim is too high and
>> we
>> miss it, but that it is too low and we reach it" (c) Michelangelo
>>
>>
>> W> Is it typical for an 2.0 application take 15 - 20 seconds to start
>> W> up, after a long period of inactivity? If not, what can I look at to
>> W> get it to start quicker, the first time it is used?
>> W>
>>
>>
>>