GC Log Analysis Tool--gchisto

0. IntroductionThe Java Performance Optimization Authority guide describes an offline analysis tool for analyzing GC logs, but there is no place to download on the official website and you need to pull it down from SVN to compile. Gchisto shows GC times, durations, and more in tabular and graphical ways, improving the efficiency of analyzing GC logs.

I. PracticeAfter the compilation is successful, the Java-jar runs directly, and the GC log. log file is add to Gchisto, and the Gchisto load log may run longer and need to wait a while.

1. Import successfully, cut to GC Pause Stats tab, can see the number of GC, GC time, GC cost, maximum GC time and minimum GC time, etc.

Garbage collection overhead (Overhead) indicates the degree of tuning of garbage collection. In general, the overhead of concurrent garbage collection should be less than 10% or 1% to 3%.

2. Cut to the GC Pause Distribution tab to see the detailed distribution of GC pauses, the X-axis represents the garbage collection pause time, and the y-axis represents the number of pauses.

It can be seen that once the remark time is about 3.6 seconds, this is worth noting what happened at the time, is the application of the problem, or the JVM parameters need tuning.

3. Switch to the GC Timeline tab to show the garbage collection on the entire timeline so that you can find the application log by time (tomcat logs, etc.) to see what happens to the system at peak time.

However, this tool does not seem to be much maintenance, there are a lot of bugs, using the process found that the JDK 1.7 gc log of the young GC, there are some nullpointer errors. As a whole, only certain parameters can be observed

GC Log Analysis Tool--gchisto