Performance Tests on G1 collector
This chapter provides tutorial notes and example codes on performance impact of G1 collector, Topics include heap footprint; heap size impact; running minor GC only, running more major GC.
These sections are omitted from this Web preview version. To view the full content,
see information on how to obtain the full version this book.
G1 GC Footprint - Free Heap 50%
Heap Size Impact on G1 GC
Heap Region Size Impact on G1 GC
Performance of G1 Minor GC
Performance of G1 Major GC
Parallel Threads Impact on G1 GC
Concurrent Threads Impact on G1 GC
AFFINITY=n - CPU Processors and G1 GC
Performance Summary of G1 Collector
- The G1 collector requires about 50% free heap space to perform
- More free heap space will increase application throughput performance.
- G1 minor GC seems to be more efficient than major GC.
- Forcing the Minor GC to "Always Tenure" results poor performance.
- Giving enough Young generation space to use Minor GC only results the best performance.
- "-XX:+G1HeapRegionSize" JVM option can be used to control
the size of heap regions used by G1 garbage collector.
- Number of GC threads should match the number of CPU processors
to get the best performance.
Table of Contents
About This Book
Heap Memory Area and Size Control
JVM Garbage Collection Logging
Introduction of Garbage Collectors
Serial Collector - "+XX:+UseSerialGC"
Parallel Collector - "+XX:+UseParallelGC"
Concurrent Mark-Sweep (CMS) Collector - "+XX:+UseConcMarkSweepGC"
Garbage First (G1) Collector - "+XX:+UseG1GC"
Object References and Garbage Collection
Garbage Collection Performance Test Program
Performance Tests on Serial Collector
Performance Tests on Parallel collector
Performance Tests on Concurrent collector
►Performance Tests on G1 collector
Garbage Collection Performance Test Summary
Full Version in PDF/EPUB