Supress the garbage collector

[Arnie]

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

[Arif Khan]

"You can remove added pressure via the RemoveMemoryPressure() method, but you
can only remove pressure you have explicitly added " i.e. by calling
AddMemoryPessure() - "you cannot lower the threshold below its default
settings."

I am quoting the above text from .NET Components (By Juval) book Page 87.

Can you please elaborate more on "more aggressive"? What are the exact side
effects you guys are noticing with the current settings.

Thanks Arif

"Arnie" wrote:

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