Hi,
I have a web site using ASP.NET and I noticed that after a long period of
inactivity, the site comes up very slowly during the first access. However,
subsequent accesses, by same or other users, is fast. I was told that this is
an IIS setting issue (goes to sleep!). Is there anythingI can do on the IIS
side to alleviate this problem?
Thanks.
Hello,
The slowness is not IIS. The first request to an ASP.NET application is
slow.
The reason you see this repeatedly is because IIS 6 (which i assume you
are using) will idle timeout when the configured time is reached (i think
default is 15 minutes). If you don't want this behavior, and you do not
need IIS to shut down the application pool, you can disable this.
But there is nothing in IIS you can do to solve the actual problem (the
first request to an ASP.NET application is slow).
--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info
Xerxes wrote:
>Hi,
>I have a web site using ASP.NET and I noticed that after a long period of
>inactivity, the site comes up very slowly during the first access. However,
>subsequent accesses, by same or other users, is fast. I was told that this
>is
>an IIS setting issue (goes to sleep!). Is there anythingI can do on the IIS
>side to alleviate this problem?
>
>Thanks.
Thanks for the info Kristofer.
When you say "the first request to ASP.NET application is slow", does that
mean the very first invocation of the application, or the first one after IIS
wakes up, every time? If it is the latter, the setting up the IIS so that it
wouldn't shut down the application pool should resolve the problem, correct?
Thanks.
"Kristofer Gafvert" wrote:
> Hello,
>
> The slowness is not IIS. The first request to an ASP.NET application is
> slow.
>
> The reason you see this repeatedly is because IIS 6 (which i assume you
> are using) will idle timeout when the configured time is reached (i think
> default is 15 minutes). If you don't want this behavior, and you do not
> need IIS to shut down the application pool, you can disable this.
>
> But there is nothing in IIS you can do to solve the actual problem (the
> first request to an ASP.NET application is slow).
>
> --
> Regards,
> Kristofer Gafvert
> http://www.gafvert.info/iis/ - IIS Related Info
>
>
> Xerxes wrote:
>
> >Hi,
> >I have a web site using ASP.NET and I noticed that after a long period of
> >inactivity, the site comes up very slowly during the first access. However,
> >subsequent accesses, by same or other users, is fast. I was told that this
> >is
> >an IIS setting issue (goes to sleep!). Is there anythingI can do on the IIS
> >side to alleviate this problem?
> >
> >Thanks.
>
It will be the first request after the application pool has started. So if
the application pool is configured to stop after being idle for a certain
amount of time, and the website is not busy, this will be a annoying
problem. Changing the settings in IIS will help.
--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info
Xerxes wrote:
>Thanks for the info Kristofer.
>When you say "the first request to ASP.NET application is slow", does that
>mean the very first invocation of the application, or the first one after
>IIS
>wakes up, every time? If it is the latter, the setting up the IIS so that
>it
>wouldn't shut down the application pool should resolve the problem,
>correct?
>
>Thanks.
>
>"Kristofer Gafvert" wrote:
>
>>Hello,
>>
>>The slowness is not IIS. The first request to an ASP.NET application is
>>slow.
>>
>>The reason you see this repeatedly is because IIS 6 (which i assume you
>>are using) will idle timeout when the configured time is reached (i think
>>default is 15 minutes). If you don't want this behavior, and you do not
>>need IIS to shut down the application pool, you can disable this.
>>
>>But there is nothing in IIS you can do to solve the actual problem (the
>>first request to an ASP.NET application is slow).
>>
>>--
>>Regards,
>>Kristofer Gafvert
>>http://www.gafvert.info/iis/ - IIS Related Info
>>
>>
>>Xerxes wrote:
>>
>>>Hi,
>>>I have a web site using ASP.NET and I noticed that after a long period of
>>>inactivity, the site comes up very slowly during the first access.
>>>However,
>>>subsequent accesses, by same or other users, is fast. I was told that
>>>this
>>>is
>>>an IIS setting issue (goes to sleep!). Is there anythingI can do on the
>>>IIS
>>>side to alleviate this problem?
>>>
>>>Thanks.
>>
Thanks again Kristofer. I will test this solution. My application pool is set
to recycle at 4 a.m. daily. I am, however, a bit hesitant to disable it
becuase I think (please correct me if I am wrong) that if I disable it, I
might get leaks (like leaving a PC running forever). Is there a way of
scripting the action of bringing up a web page at some point in time? If my
application pool is recycled at 4 a.m., maybe I can bring a page up at 4:15
a.m.
"Kristofer Gafvert" wrote:
> It will be the first request after the application pool has started. So if
> the application pool is configured to stop after being idle for a certain
> amount of time, and the website is not busy, this will be a annoying
> problem. Changing the settings in IIS will help.
>
>
>
> --
> Regards,
> Kristofer Gafvert
> http://www.gafvert.info/iis/ - IIS Related Info
>
>
> Xerxes wrote:
>
> >Thanks for the info Kristofer.
> >When you say "the first request to ASP.NET application is slow", does that
> >mean the very first invocation of the application, or the first one after
> >IIS
> >wakes up, every time? If it is the latter, the setting up the IIS so that
> >it
> >wouldn't shut down the application pool should resolve the problem,
> >correct?
> >
> >Thanks.
> >
> >"Kristofer Gafvert" wrote:
> >
> >>Hello,
> >>
> >>The slowness is not IIS. The first request to an ASP.NET application is
> >>slow.
> >>
> >>The reason you see this repeatedly is because IIS 6 (which i assume you
> >>are using) will idle timeout when the configured time is reached (i think
> >>default is 15 minutes). If you don't want this behavior, and you do not
> >>need IIS to shut down the application pool, you can disable this.
> >>
> >>But there is nothing in IIS you can do to solve the actual problem (the
> >>first request to an ASP.NET application is slow).
> >>
> >>--
> >>Regards,
> >>Kristofer Gafvert
> >>http://www.gafvert.info/iis/ - IIS Related Info
> >>
> >>
> >>Xerxes wrote:
> >>
> >>>Hi,
> >>>I have a web site using ASP.NET and I noticed that after a long period of
> >>>inactivity, the site comes up very slowly during the first access.
> >>>However,
> >>>subsequent accesses, by same or other users, is fast. I was told that
> >>>this
> >>>is
> >>>an IIS setting issue (goes to sleep!). Is there anythingI can do on the
> >>>IIS
> >>>side to alleviate this problem?
> >>>
> >>>Thanks.
> >>
>
Hi,
Do you have a reason to recycle the application pool daily? Or is this a
"just-in-case" action?
Personally, i would just let it run, and if i later notice problems, i
would deal with it at that time.
Scripting is not my area of expertise. I would just write a small
application that does a HTTP GET and schedule the application to run at a
specified time (using Scheduled Tasks).
--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info
Xerxes wrote:
>Thanks again Kristofer. I will test this solution. My application pool is
>set
>to recycle at 4 a.m. daily. I am, however, a bit hesitant to disable it
>becuase I think (please correct me if I am wrong) that if I disable it, I
>might get leaks (like leaving a PC running forever). Is there a way of
>scripting the action of bringing up a web page at some point in time? If my
>application pool is recycled at 4 a.m., maybe I can bring a page up at 4:15
>a.m.
>
>"Kristofer Gafvert" wrote:
>
>>It will be the first request after the application pool has started. So if
>>the application pool is configured to stop after being idle for a certain
>>amount of time, and the website is not busy, this will be a annoying
>>problem. Changing the settings in IIS will help.
>>
>>
>>
>>--
>>Regards,
>>Kristofer Gafvert
>>http://www.gafvert.info/iis/ - IIS Related Info
>>
>>
>>Xerxes wrote:
>>
>>>Thanks for the info Kristofer.
>>>When you say "the first request to ASP.NET application is slow", does
>>>that
>>>mean the very first invocation of the application, or the first one after
>>>IIS
>>>wakes up, every time? If it is the latter, the setting up the IIS so that
>>>it
>>>wouldn't shut down the application pool should resolve the problem,
>>>correct?
>>>
>>>Thanks.
>>>
>>>"Kristofer Gafvert" wrote:
>>>
>>>>Hello,
>>>>
>>>>The slowness is not IIS. The first request to an ASP.NET application is
>>>>slow.
>>>>
>>>>The reason you see this repeatedly is because IIS 6 (which i assume you
>>>>are using) will idle timeout when the configured time is reached (i
>>>>think
>>>>default is 15 minutes). If you don't want this behavior, and you do not
>>>>need IIS to shut down the application pool, you can disable this.
>>>>
>>>>But there is nothing in IIS you can do to solve the actual problem (the
>>>>first request to an ASP.NET application is slow).
>>>>
>>>>--
>>>>Regards,
>>>>Kristofer Gafvert
>>>>http://www.gafvert.info/iis/ - IIS Related Info
>>>>
>>>>
>>>>Xerxes wrote:
>>>>
>>>>>Hi,
>>>>>I have a web site using ASP.NET and I noticed that after a long period
>>>>>of
>>>>>inactivity, the site comes up very slowly during the first access.
>>>>>However,
>>>>>subsequent accesses, by same or other users, is fast. I was told that
>>>>>this
>>>>>is
>>>>>an IIS setting issue (goes to sleep!). Is there anythingI can do on the
>>>>>IIS
>>>>>side to alleviate this problem?
>>>>>
>>>>>Thanks.
>>>>
>>