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 Young GC only, running more Full GC and Old 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 4% to 50%
Heap Size Impact on G1 GC
Heap Region Size Impact on G1 GC
Object Size Impact on G1 Young GC
Parallel Threads Impact on G1 Young GC
Object Size Impact on G1 Full GC
Object Size Impact on G1 Old GC
Concurrent Threads Impact on G1 Old GC
Parallel Threads Impact on G1 Old GC
CPU Processors Impact on G1 Old GC
Performance Summary of G1 Collector
- The G1 collector requires about 4% free heap space to perform
- More free heap space will increase application throughput performance.
- Heap region size seems to have no impact on application throughput performance.
- G1 Young GC can process about 42 MB objects per ms with object size of 1K.
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"
The Z Garbage Collector (ZGC) - "+XX:+UseZGC"
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