We are currently using the IIS 6.0 default settings for application
pools. In particular we have the idle time(?) for recycling set to 20
mins. All our applications are ASP.NET 2.0. Given the hit you get
with this when everything reloads for the first time for ASP.NET, we
were wondering what the downside of turning this off would be? Or to
put it another way, why does this option exist?
Thanks
Matt
Hello,
This is useful on a shared server with many application, where many of
them being idle often. Using this feature it means that more applications
(customers) can run on the same server.
If you have the resources and don't need to shut down the worker process
to save on them, leave it running.
--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info
winnmp@hotmail.com wrote:
>We are currently using the IIS 6.0 default settings for application
>pools. In particular we have the idle time(?) for recycling set to 20
>mins. All our applications are ASP.NET 2.0. Given the hit you get
>with this when everything reloads for the first time for ASP.NET, we
>were wondering what the downside of turning this off would be? Or to
>put it another way, why does this option exist?
>
>Thanks
>
>
>Matt
The option exists because there are circumstances that make the option
useful. Idle timeout allows reclaim of resources so that you can
potentially run more code than you can simultaneously.
In the case of dedicated servers, if you have provisioned the server
hardware to be sufficient for your application, then idle timeout is
clearly unnecessary and probably detrimental to performance/
reliability.
However, in the case of shared hosting, idle timeout allows you to
pack thousands of users and their websites onto one box to maximize
utilization of resources by ACTIVE applications.
Since IIS6 is a generic and configurable server, it needs to have
options to handle these and MORE diverse workloads.
Obviously, not all options are optimal for all applications -- if that
was the case, one never needs to tune settings. Nor are the defaults
guaranteed to be best for any given application.. In particular, the
defaults are tuned towards ASP/COM applications, which completely
contradict with hosting ASP.Net applications. Thus, you always have to
understand and tune such settings depending on your circumstance.
Basically, IIS assumes that for users that care about these settings,
they will figure out what to customize and with what values. If the
user does not care, then the defaults are by definition sufficient. It
doesn't matter if the defaults are not optimal if the user does not
care about it either. Optimal behavior requires user interaction.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On Jul 12, 2:59 pm, win...@hotmail.com wrote:
> We are currently using the IIS 6.0 default settings for application
> pools. In particular we have the idle time(?) for recycling set to 20
> mins. All our applications are ASP.NET 2.0. Given the hit you get
> with this when everything reloads for the first time for ASP.NET, we
> were wondering what the downside of turning this off would be? Or to
> put it another way, why does this option exist?
>
> Thanks
>
> Matt