Bug in G1 logging?

Thomas Schatzl thomas.schatzl at oracle.com
Mon Jun 15 09:26:36 UTC 2015


Hi,

On Mon, 2015-06-15 at 10:52 +0200, Thomas Viessmann wrote:
> Sure:
> 
> CommandLine flags: -XX:+DisableExplicitGC -XX:
> +ExplicitGCInvokesConcurrent -XX:G1LogLevel=finest -XX:
> +G1SummarizeRSetStats -XX:G1Summari
> zeRSetStatsPeriod=1 -XX:+G1TraceReclaimDeadHumongousObjectsAtYoungGC
> -XX:GCLogFileSize=104857600 -XX:+HeapDumpOnOutOfMemoryError -XX:Hea
> pDumpPath=/icebackups/DashboardFiles/logs
> -XX:InitialHeapSize=25769803776 -XX:MaxGCPauseMillis=400
> -XX:MaxHeapSize=25769803776 -XX:MaxMe
> taspaceSize=536870912 -XX:MetaspaceSize=268435456
> -XX:NumberOfGCLogFiles=10 -XX:+ParallelRefProcEnabled -XX:
> +PrintAdaptiveSizePolicy -XX
> :+PrintGC -XX:+PrintGCCause -XX:+PrintGCDateStamps -XX:+PrintGCDetails
> -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC -XX:+PrintTenuringDistr
> ibution -XX:+UnlockDiagnosticVMOptions -XX:
> +UnlockExperimentalVMOptions -XX:+UseCompressedClassPointers -XX:
> +UseCompressedOops -XX:+UseG
> 1GC -XX:+UseGCLogFileRotation 
> 
> Java HotSpot(TM) 64-Bit Server VM (25.40-b25) for linux-amd64 JRE
> (1.8.0_40-b25), built on Feb 10 2015 21:29:53 by "java_re" with gcc 4.
> 3.0 20080428 (Red Hat 4.3.0-8)
> Memory: 4k page, physical 65743256k(31795400k free), swap
> 16777208k(16777208k free)
> 
> 
-XX:+G1SummarizeRSetStats -XX:G1SummarizeRSetStatsPeriod=1 most likely
causes this. While it is quite useful for diagnosis, it takes quite a
bit of time to gather the necessary information.

Thanks,
  Thomas




More information about the hotspot-gc-dev mailing list