Fragmentation and UseCMSInitiatingOccupancyOnly

[Bernd Eckenfels]

If You set the percentage low, the Risk is, that oldgen will be permanently over the threshold (this might be wanted?). If you set it high, then AF might happen due to fragmentation or background collection beeing too slow.

 I think fragmentation is not honored, therefore your desired oldheap size should account for that an have plenty of (untouched) headroom.

Bernd

> Am 22.01.2014 um 12:12 schrieb Gustav Åkesson <gustav.r.akesson at gmail.com>:
> 
> Hi,
>  
> In case UseCMSInitiatingOccupancyOnly is enabled we instruct CMS to start at X% of old gen, and not try to figure out by itself when to start. My understanding is that when flag is disabled, CMS is aiming for X%, but uses statistics of previous collections (GC rate, GC time) to determine when to initiate.
>  
> My question is whether enabling UseCMSInitiatingOccupancyOnly increases the risk of promotion failure (FullGC) due to fragmentation, meaning that it will always honor X% rule and rather generate promotion failure event than run CMS prematurely?
>  
> Or, in case flag is disabled, is CMS smart enough to start prior to X% when heap is fragmented instead of generating promotion failure?
>  
>  
> Best Regards,
>  
> Gustav Åkesson
> _______________________________________________
> hotspot-gc-use mailing list
> hotspot-gc-use at openjdk.java.net
> http://mail.openjdk.java.net/mailman/listinfo/hotspot-gc-use