Enabling GC logging provides great benefits such as: reducing overall application response time, troubleshooting memory problems, forecast outages, and doing effective capacity planning… Contrary to common thinking, enabling GC logging doesn’t add any noticeable overhead to your application. Thus, we strongly recommend you enable GC logging on all your production servers.
Continue reading “WHAT IS GARBAGE COLLECTION LOG? HOW TO ENABLE & ANALYZE?”
Based on the JVM version (1.4, 5, 6, 7, 8, 9), JVM vendor (Oracle, IBM, HP, Azul, Android), GC algorithm (Serial, Parallel, CMS, G1, Shenandoah) and few other settings, GC log format changes. Thus, today the world has ended up with several GC log formats.
Continue reading “GC LOG STANDARDIZATION API”
Our Garbage collection log analysis REST API provides powerful micrometrics. Using these micrometrics, you can predict and forecast the application’s availability and performance characteristics.
Continue reading “GARBAGE COLLECTION LOG ANALYSIS API”
To diagnose any memory problems, Garbage Collection log file is the best place to start. It provides several interesting statistics:
Continue reading “UNDERSTANDING GARBAGE COLLECTION LOG”