I ran a production server with recycling disabled for weeks
on end. I did
some in-memory logging (dictionary) and that was causing
high memory usage
when things were going wrong, but the advantage was that I
could run
"services" inside asp.net and some of those
services would run on a schedule
(like a cron job) and clean up the in-memory logging by
filtering out needed
information to database and removing the rest from memory
(like debugging
info). Even though it had a fair amount of traffic I
wouldn't have
considered it a high traffic site. It did, however, do an
awful lot of
processing 24/7 (I moved windows services into the asp.net
domain for web
administration). There was no unsafe or unmanaged code.
Regards,
Brian
On 12/13/06, Ryan Heath <ryan.q.heath gmail.com> wrote:
>
> Hi,
>
> Is there still any reason to recycle 100% .net web
apps?
>
> At the time when our website was a hybrid of VB/COM/C++
we needed to
> recycle the pool, to get rid off memory fragmentation,
but with .net,
> this should not be needed, is it?
>
> The real reason I ask, is that we have a high traffic
site, with
> several webservers.
> Now, when one is starting to recycle, it is noticeable.
And due to our
> installation scripts, the servers will recycle almost
all together...
> ouch!
>
> I was looking for a way to, maybe, schedule the
recycles, but then I
> thought, why do we still recycle the pools?
>
> // Ryan
>
> ===================================
> This list is hosted by DevelopMentor(r) http://www.develop.com
>
> View archives and manage your subscription(s) at
> http://discuss.develop.com
>
===================================
This list is hosted by DevelopMentorŪ http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
|