A GC cycle may be exhaustive and may slow down your application for that duration when its on go.... We have observed it for some cases...
The new JVMs have some more -XX options to play around with GC algorithm so try those options before you think of using System.gc() call.
I am unclear what you are tyring to say here.
But there is no GC cycle as such.
And how have you observed it?
The -XX options requires more expertise and experience than the System.gc() call.
And I think there is no harm in calling the System.gc(), because you only request GC. Its not certain that GC will happen.
Originally posted by Ankit G@rg:
SomeClass o = new SomeClass();
//o is not needed any more
o = null; //good as you still have a lot of processing to do
://a lot of processing