harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiao-Feng Li" <xiaofeng...@gmail.com>
Subject Re: [General VM] GC strategy:how to garbage collect short-lived objects quickly.
Date Thu, 14 Sep 2006 23:51:04 GMT
On 9/15/06, Ivan Volosyuk <ivan.volosyuk@gmail.com> wrote:
> Well, common practise is to allocate most of the physical memory for
> java heap and let the GC to deal with it. Different GC algorithms will
> produce different pause times with different frequencies.
> For your case, I think, it will be optimal to have old generation of
> objects living untouched most of the GCs. The rest of the heap is for
> young generation objects. GC can be made to occur more frequently if
> we collect only part of the young generation space: the oldest chunk
> of young generation at a time. There is a trade-off between portion of
> heap collected and GC frequency, of cause.
> Other techniques like the JIT's thread-local allocation can also help.
> --
> Ivan

Yes, agreed. the trade-off in GC frequency should be well understood
in order to achieve best performance.


Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org

View raw message