Did any one encountered a scenario where application under high memory allocation load performed second generation collection every 100 seconds ?
We using 64-bit server
I assume this is for .net.
GC collects when it wants to base on its algorithm. You can suggest the garbage collector to collect but it may not actually do anything.
you can use GC.Collect() to ask the GC to look if garbage can be collected. However it may not actually remove items from memory.
NOTE: Also, make sure you are clearing references correctly. Meaning unhooking events, Clearing references between objects. This will help the GC in collected objects that are no longer in scope.