Hey Folks,

I know this is taboo but we have a long running highly availble app that is
being affected by the garbage collector.

In .NET 1.1 there were issues because of the aggressive GC and under 2.0 it
appears much worse (i.e. the garbage collector is even more aggressive).

We have noticed that there are the Add/RemoveMemoryPressure hints to the GC
with the amount of unmanaged memory allocated.

Can these be used as tricks to make the GC less aggressive?

Any other ideas without actually going back to the unmanaged world?
Would just making things unsafe in critical areas and doing the memory
management ourselves make more sense?

-arnie

My Suggestion would be is to not to tweak around with GC because the
CLR GC is tuned for very well. In spite of this if you need to change
the way in GC collects the manage heap is using the hosting interface
ICLRGCManager (available only .NET 2.0).

Explain what you mean by this.

--
Warm Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Professional VSTO 2005 - Wrox/Wiley 2006
Blog: http://msmvps.com/blogs/Alvin/
-------------------------------------------------------



"Arnie" <jefferyronaldarnett (AT) msn (DOT) com> wrote