Performance Tests on Parallel collector
This chapter provides tutorial notes and example codes on performance impact of Parallel 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.
Parallel GC Footprint - Free Heap 10%
Heap Size Impact on Parallel GC
Parallel Minor GC Not Removing Dead Objects
Performance of Parallel Minor GC
Performance of Parallel Major GC
"-XX:MaxTenuringThreshold=0" - Bad for Parallel GC
Tiny Survivor Spaces Are Bad for Parallel GC
Thread Count Impact on Parallel GC
AFFINITY=n - CPU Processors and Parallel GC
Best Parallel GC Configuration
Performance Summary of Parallel Collector
- The Parallel collector requires about 10% free heap space to perform
- More free heap space will increase application throughput performance.
- Parallel 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.
- 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