David
Fri Jan 13 05:05:13 CST 2006
I think you should start with the defaults and make one modification
specifically to deal with your large-memory consumption.
To me, if the issue is large-memory consumption, it makes sense to just set
IIS's memory-limit heuristic to some large value which if reached means that
too much memory was happening... but definitely not so small that you
false-trigger the recycle. Because as soon as the heuristic is triggered,
IIS automatically shuts the old w3wp.exe down and bring up a new w3wp.exe
immediately, as necessary.
Thus, setting periodic restart to 5 minutes is not so good because:
1. not only is it restarting the app pool LESS quickly than the actual
memory heuristic which caused the recycle (you are merely guaranteeing a
recycle every 5 minutes; the heuristic-triggered recycle will guarantee it
immediately)
2. it also forces your applications to only have 5 minutes worth of data
caching -- which for a synchronous application like PHP and MySQL, you are
working against their attempts to improve performance through caching and
could cause additional work to be done, which may increase the possibility
of high memory usage... which triggers the recycle more frequently and goes
down a death spiral.
Also, can you explain WHY you are using Web Garden.
Finally, I think you need to investigate WHY you are getting the
large-memory consumption issue... because health monitoring is meant to buy
you time to hobble along to find and fix the issue. You should not depend on
it as a long-term crutch because it simply removes one way to buy you more
time in the future.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Paul G" <PaulG@discussions.microsoft.com> wrote in message
news:95490A5E-A6C5-4662-86E0-C04FFD491475@microsoft.com...
>I changed them because of the memory issue I was having.
>
> I set it at 5 minutes because when the memory issued occured I needed a
> way
> for the server to restart the app pool more quickly. With the default it
> would be a really long time before the server would be responsive again.
> And
> since this is a remote server, I couldn't even remote desktop in to stop
> the
> processes.
>
> I set the memory low because I was using 10 worker processes and didn't
> want
> to overload the ram.
>
> So that being said, should I still stay with the defaults?