Really helpful!

The recommendation is to use "-XX:+UseStringDeduplication" yet it's clear from the logs that I already have that flag turned on by these log lines: [String Dedup Fixup: 12.5 ms, GC Workers: 20] [Queue Fixup (ms): Min: 0.0, Avg: 0.0, Max: 0.0, Diff: 0.0, Sum: 0.0] [Table Fixup (ms): Min: 12.0, Avg: 12.2, Max: 12.3, Diff: 0.3, Sum: 243.1]

thank you for creating this tool to analyse the GC log files. I found it very easy to read and it makes reading the GC logs a lot more easier!

thank you for creating this tool to analyse the GC log files. I found it very easy to read and it makes reading the GC logs a lot more easier!

thank you for creating this tool to analyse the GC log files. I found it very easy to read and it makes reading the GC logs a lot more easier!

Good one.

thank you for creating this tool to analyse the GC log files. I found it very easy to read and it makes reading the GC logs a lot more easier!

I thought there was a (kind of) memory leak after changing to CMS-GC : much more variations in heap usage than with previous //GC (not in this logfile but memory usage went up to 100% - a 3 hour linear ramping up in the night with no obvious cause - very little server activity) note : I am using your tool for the first time, seems really practical. I have not already made the decision to subscribe (internal decision) and would like just now to download this report as free but it looks as if this doesn't work. :(

thank you for creating this tool to analyse the GC log files. I found it very easy to read and it makes reading the GC logs a lot more easier!

good