Performance Tests on Concurrent collector
This chapter provides tutorial notes and example codes on performance impact of Concurrent collector, Topics include heap footprint; heap size impact; running Young GC only; running more Old GC; impact of parallel threads; impact of concurrent threads.
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.
Concurrent GC Footprint - Free Heap 4%
Heap Size Impact on Concurrent GC
Performance of Concurrent Young GC
Performance of Concurrent Full GC
Performance of Concurrent Old GC
Parallel Threads Impact on Concurrent GC
Concurrent Threads Impact on Concurrent GC
AFFINITY=n - CPU Processors and Concurrent GC
Best Concurrent GC Configuration
Performance Summary of Concurrent Collector
- The Concurrent collector requires about 4% free heap space to perform
- More free heap space will increase application throughput performance.
- Concurrent Young GC seems to be more efficient than Old GC.
- Giving enough Young generation space to use Young GC only results the best performance.
- Number of parallel GC threads has no impact on the performance.
- Number of concurrent GC threads has no impact on the 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"
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