Avoiding 1 long CMS with a big heap

[Matt Khan]

>> CMS tries to project how early to start a cycle based on past behavior. 
 When there hasn't been much data gathered about collections, the 
projection can just be wrong.
OK so it seems to be Q of how can I mitigate this risk, i.e. is there 
anything I can do to influence this behaviour such that the probability of 
such an incorrect call, by the collector, is reduced? 

Obviously ideally it would be possible to eliminate the risk full stop but 
based on your reply it sounds like I'd need to be able to guarantee that 
"this object really is not reachable by anything that's in tenured" which 
really appears to equate to explicit memory management.

Cheers
Matt

Matt Khan
--------------------------------------------------
GFFX Auto Trading
Deutsche Bank, London



---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/hotspot-gc-use/attachments/20100414/bbd3601f/attachment-0001.html