CMS collection keep working during holiday

[Ken--@newsgroupstats.hk]

I have added XX: SoftRefLRUPolicyMSPerMB=0 and the result is the same. :-(

VM optoins: -Djava.security.policy=.\java.policy -Xms1536M -Xmx1536M
-XX:NewSize=256M -XX:+PrintGCDetails -XX:+PrintGCTaskTimeStamps
-XX:+PrintHeapAtGC -Xloggc:gc.log -XX:+PrintReferenceGC
-XX:+DisableExplicitGC -XX:+UseConcMarkSweepGC -XX:+UseParNewGC
-XX:SurvivorRatio=4 -XX:CMSInitiatingOccupancyFraction=55
-XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=0
-Dcom.sun.management.jmxremote.port=18002
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false 

I have adjusted the XX:CMSInitiatingOccupancyFraction to 55 this time. 

Please ignore the last full gc in the chart. The full gc is triggered by
jmap -histo:live.

http://www.nabble.com/file/p19893088/jconsole_20081009.jpg 

http://www.nabble.com/file/p19893088/gc.log gc.log 









Jon Masamitsu wrote:
> 
> Ken,
> 
> One of the differences between the CMS concurrent
> collection of the old gen and a full collection
> (concurrent mode fail) is the way SoftReferences
> are processed when the heap is full of live data.
> A full collection will clear all SoftReferences
> before it throws an out-of-memory.  If a full
> collection is done and the heap is still full
> of live data, a full collection will clear all
> SoftReferences.  When CMS does a concurrent
> collection and the heap is still full, a
> concurrent mode failure occurs resulting in
> a full collection.  And as with full collections,
> all the SoftReferences will be cleared if
> necessary.  If you set -XX: SoftRefLRUPolicyMSPerMB=0
> SoftReferences will be cleared promptly and should
> tell us if we're encountering this difference in
> the way SoftReferences are handled.
> 
> Jon
> 
> 

-- 
View this message in context: http://www.nabble.com/CMS-collection-keep-working-during-holiday-tp19773575p19893088.html
Sent from the OpenJDK Hotspot Garbage Collection mailing list archive at Nabble.com.