Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (13)
Similar to -XX:+UseG1GC
Similar to -XX:+UseG1GC (20)
More from Jakub Kubrynski
Recently uploaded
Recently uploaded (20)
-XX:+UseG1GC
- 2. @jkubrynskijk@devskiller.com Who are we? - Me - $ since 2004 - Co-Founder of DevSKiller.com + Codearte.io - JVM passionate - Trainer @ Bottega - You - Java developers? - GC logs analysts? - JVM tuners?
- 3. @jkubrynskijk@devskiller.com Why all this mess? Because applications need memory... … and memory is limited Developers are too lazy to manage memory manually... … and Garbage Collector has a limited performance and a need to stop the world
- 4. @jkubrynskijk@devskiller.com Vector algorithm mark_gc_roots() for (each_root_object) { mark_all_referenced_objects() } for (each_object_in_memory) { if (is_marked_as_reacheable) { unmark_the_object() } else { remove_object_and_reclaim_memory() } }
- 17. @jkubrynskijk@devskiller.com Important terms Collection Set (CSet) Root Regions
- 18. @jkubrynskijk@devskiller.com Collections in G1 Young collection Background concurrent cycle Mixed collection Full GC
- 19. @jkubrynskijk@devskiller.com Young GC Triggered after filling all Eden regions Parallel Stop-The-World
- 20. @jkubrynskijk@devskiller.com Concurrent cycle Piggybacked on Young GC, which works as a initial- mark Looks for easiest regions to clean (min live objects) - concurrent-root-region-scan - concurrent-mark - concurrent-cleanup
- 21. @jkubrynskijk@devskiller.com Mixed GC Regions marked in the previous step are cleaned during mixed collections Young generation + part of old Processes - min => marked regions count / G1MixedGCCountTarget - max => 10% of all regions
- 22. @jkubrynskijk@devskiller.com Full GC Veeery slow serial collector Cleans everything
- 24. @jkubrynskijk@devskiller.com G1 Tuning – the dark side G1ConcMarkForceOverflow G1ConcMarkStepDurationMillis G1ConcRSHotCardLimit G1ConcRSLogCacheSize G1ConcRefinementGreenZone G1ConcRefinementRedZone G1ConcRefinementServiceIntervalMillis G1ConcRefinementThreads G1ConcRefinementThresholdStep G1ConcRefinementYellowZone G1ConcRegionFreeingVerbose G1ConfidencePercent G1DummyRegionsPerGC G1EvacuationFailureALot G1EvacuationFailureALotCount G1EvacuationFailureALotDuringConcMark G1EvacuationFailureALotDuringInitialMark G1EvacuationFailureALotDuringMixedGC G1EvacuationFailureALotDuringYoungGC G1EvacuationFailureALotInterval G1ExitOnExpansionFailure G1FailOnFPError G1HRRSFlushLogBuffersOnVerify G1HRRSUseSparseTable G1HeapRegionSize G1HeapWastePercent G1MarkingOverheadPercent G1MarkingVerboseLevel G1MaxVerifyFailures G1MixedGCCountTarget G1PrintHeapRegions G1PrintRegionLivenessInfo G1RSBarrierRegionFilter G1RSScrubVerbose G1RSetRegionEntries G1RSetRegionEntriesBase G1RSetScanBlockSize G1RSetSparseRegionEntries G1RSetSparseRegionEntriesBase G1RSetUpdatingPauseTimePercent G1RecordHRRSEvents G1RecordHRRSOops G1RefProcDrainInterval G1ReservePercent G1SATBBufferEnqueueingThresholdPercent G1SATBBufferSize G1SATBProcessCompletedThreshold G1ScrubRemSets G1SecondaryFreeListAppendLength G1StressConcRegionFreeing G1StressConcRegionFreeingDelayMillis G1SummarizeConcMark G1SummarizeRSetStats G1SummarizeRSetStatsPeriod G1TraceConcRefinement G1TraceHeapRegionRememberedSet G1TraceMarkStackOverflow G1UpdateBufferSize G1UseAdaptiveConcRefinement G1VerifyBitmaps G1VerifyCTCleanup G1VerifyHeapRegionCodeRoots G1VerifyRSetsDuringFullGC G1YoungSurvRateNumRegionsSummary G1YoungSurvRateVerbose PrintCFG1
- 26. @jkubrynskijk@devskiller.com Humongous Humongous > ½ G1RegionSize G1 Humongous Allocation can cause Major GC Humongous is evil Eliminate them by extending region size
- 27. @jkubrynskijk@devskiller.com What else should we look for? Concurrent mode failure Promotion failure Evacuation failure
- 28. @jkubrynskijk@devskiller.com Logs [GC pause (G1 Evacuation Pause) (young), 0.2611788 secs] [Parallel Time: 257.3 ms, GC Workers: 8] [GC Worker Start (ms): Min: 32183.4, Avg: 32185.5, Max: 32196.3, Diff: 12.9] [Ext Root Scanning (ms): Min: 0.0, Avg: 0.4, Max: 0.8, Diff: 0.8, Sum: 2.8] [Update RS (ms): Min: 7.2, Avg: 18.4, Max: 27.2, Diff: 20.0, Sum: 147.3] [Processed Buffers: Min: 5, Avg: 10.2, Max: 17, Diff: 12, Sum: 82] [Scan RS (ms): Min: 79.1, Avg: 85.6, Max: 87.3, Diff: 8.1, Sum: 684.9] [Code Root Scanning (ms): Min: 0.0, Avg: 0.0, Max: 0.0, Diff: 0.0, Sum: 0.0] [Object Copy (ms): Min: 148.3, Avg: 148.9, Max: 150.8, Diff: 2.5, Sum: 1190.9] [Termination (ms): Min: 0.0, Avg: 1.8, Max: 2.1, Diff: 2.1, Sum: 14.7] [GC Worker Other (ms): Min: 0.0, Avg: 0.0, Max: 0.0, Diff: 0.0, Sum: 0.1] [GC Worker Total (ms): Min: 244.3, Avg: 255.1, Max: 257.2, Diff: 12.9, Sum: 2040.8] [GC Worker End (ms): Min: 32440.6, Avg: 32440.6, Max: 32440.6, Diff: 0.0] [Code Root Fixup: 0.0 ms] [Code Root Purge: 0.0 ms] [Clear CT: 0.1 ms] [Other: 3.8 ms] [Choose CSet: 0.0 ms] [Ref Proc: 0.2 ms] [Ref Enq: 0.0 ms] [Redirty Cards: 0.6 ms] [Humongous Reclaim: 0.0 ms] [Free CSet: 2.2 ms] [Eden: 172.0M(172.0M)->0.0B(173.0M) Survivors: 25.0M->25.0M Heap: 1912.0M(3940.0M)->1870.0M(3972.0M)] [Times: user=2.00 sys=0.02, real=0.26 secs]
- 31. @jkubrynskijk@devskiller.com Will stay default in JDK 9? Kirk Pepperdine: Using G1 is known to corrupt Lucene indexes Charlie Hunt: Does the term "known" imply past tense? ;-) You know I'm just having a little fun with you, right? Kirk Pepperdine: Dude, seriously.. Stefan Johansson: A short heads up. The change to make G1 the default garbage collector has now made its way to jdk9/dev and should soon be part of a JDK 9 early access build.