First time access to website is slow - Solutions?

[Cirene]

As I understand it, (by design?) the first person to visit a ASP.NET website
has to wait a little longer because the site is being compiled. Subsequent
visitors (if they visit soon) will find the site to load faster. After like
30 minutes this happens again. Where can I change this setting (that caches
the compiled website)? If my hosting company won't change it are there
other solutions to keep the site alive/active regularly (even a service that
"visits" every 25 min or something)?

Thanks for your insight!

[derhamfamily]

On 13 Nov, 20:11, "Cirene" <[e-mail] rote:

As I understand it, (by design?) the first person to visit a ASP.NET website
has to wait a little longer because the site is being compiled. Subsequent
visitors (if they visit soon) will find the site to load faster. After like
30 minutes this happens again. Where can I change this setting (that caches
the compiled website)? If my hosting company won't change it are there
other solutions to keep the site alive/active regularly (even a service that
"visits" every 25 min or something)?

Thanks for your insight!

Maybe you should try the aspnet compiler before you deploy to your
host.

check it out here: http://msdn2.microsoft.com/en-us/lib...63(VS.80).aspx

[Cirene]

But it's already compiled. I use Visual Studio.net 2005. (Sorry if I
didn't explain that well.)

My hosting company support stated "Please be sure that the compiled cached
on server is a behavior of Microsoft ASP.NET, we can not change this kind of
cache. The only thing we can do is keep the compiled application loaded on
the cache, therefore a scheduled task can be help to keep the cache stay.
Thank you."

Make sense?

<de**********@g ooglemail.comwr ote in message
news:11******** **************@ o80g2000hse.goo glegroups.com.. .

On 13 Nov, 20:11, "Cirene" <[e-mail] rote:

>As I understand it, (by design?) the first person to visit a ASP.NET
website
has to wait a little longer because the site is being compiled.
Subsequent
visitors (if they visit soon) will find the site to load faster. After
like
30 minutes this happens again. Where can I change this setting (that
caches
the compiled website)? If my hosting company won't change it are there
other solutions to keep the site alive/active regularly (even a service
that
"visits" every 25 min or something)?

Thanks for your insight!

Maybe you should try the aspnet compiler before you deploy to your
host.

check it out here:
http://msdn2.microsoft.com/en-us/lib...63(VS.80).aspx

[codezilla94]

On Nov 13, 4:00 pm, "Cirene" <[e-mail] rote:

But it's already compiled. I use Visual Studio.net 2005. (Sorry if I
didn't explain that well.)

My hosting company support stated "Please be sure that the compiled cached
on server is a behavior of MicrosoftASP.NE T, we can not change this kind of
cache. The only thing we can do is keep the compiled application loaded on
the cache, therefore a scheduled task can be help to keep the cache stay.
Thank you."

Make sense?

<derhamfam...@g ooglemail.comwr ote in message

news:11******** **************@ o80g2000hse.goo glegroups.com.. .

On 13 Nov, 20:11, "Cirene" <[e-mail] rote:

As I understand it, (by design?) thefirstperson to visit aASP.NET
website
has to wait a little longer because the site is being compiled.
Subsequent
visitors (if they visit soon) will find the site toloadfaster. After
like
30 minutes this happens again. Where can I change this setting (that
caches
the compiled website)? If my hosting company won't change it are there
other solutions to keep the site alive/active regularly (even a service
that
"visits" every 25 min or something)?

Thanks for your insight!

Maybe you should try the aspnet compiler before you deploy to your
host.

check it out here:
http://msdn2.microsoft.com/en-us/lib...3(VS.80).aspx- Hide quoted text -

- Show quoted text -

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/ViewSo...2-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.

[=?Utf-8?B?UGV0ZXIgQnJvbWJlcmcgW0MjIE1WUF0=?=]

Actually you can make the application itself do the "ping request".
In the Application_End handler in Global.asax, just put in a WebClient
request for the site.

--Peter
"Inside every large program, there is a small program trying to get out."
http://www.eggheadcafe.com
http://petesbloggerama.blogspot.com
http://www.blogmetafinder.com

"unknown" wrote:

>