GC Easy Tool review

(Reviews written by the users after using the tool)

Star Ratings

2229 Ratings

4.78 out of 5 stars

5 star
85.3%
4 star
10.5%
3 star
2.4%
2 star
0.9%
1 star
1.0%

User Comments


2017-06-23

Got first valueable results within seconds! - Thumbs up!


2017-06-23

Excellent tool. Saved me humongous time which was being spent in scanning through the GC logs, graphing etc.


2017-06-20
By koszycki.wojciech

Great job guys !


2017-06-19
By chandukreddi

I have this information in my GC log but it didn;t show this information here . Pause time 3 sec but this report don;t show that information. 2017-06-09T16:24:08.842+0000: 225636.648: Total time for which application threads were stopped: 0.0110163 seconds 2017-06-09T16:25:58.653+0000: 225746.459: Total time for which application threads were stopped: 3.0282261 seconds 2017-06-09T16:25:59.654+0000: 225747.460: Total time for which application threads were stopped: 0.0007739 seconds 2017-06-09T16:26:02.253+0000: 225750.059: Total time for which application threads were stopped: 0.0025527 seconds {Heap before GC invocations=25641 (full 3):


2017-06-19
By chandukreddi

I have this information in my GC log but it didn;t show this information here . Pause time 3 sec but this report don;t show that information. 2017-06-09T16:24:08.842+0000: 225636.648: Total time for which application threads were stopped: 0.0110163 seconds 2017-06-09T16:25:58.653+0000: 225746.459: Total time for which application threads were stopped: 3.0282261 seconds 2017-06-09T16:25:59.654+0000: 225747.460: Total time for which application threads were stopped: 0.0007739 seconds 2017-06-09T16:26:02.253+0000: 225750.059: Total time for which application threads were stopped: 0.0025527 seconds {Heap before GC invocations=25641 (full 3):


2017-06-19

simply a nice tool, with a good overveiw


2017-06-16

your report indicates there were no consecutive full GCs,. Consecutive full GCs do occur in the log file I was looking at. It doesn't indicate any real problems, memory or otherwise, but near the end of the logfile the JVM was shorter on availble memory than I like and Full GCs were being triggered rapidly while not freeing much (compared to the average partial GC). I don't consider that to be a sign of a healthy app. The GC problems at the end of the log arn't what I was looking at or for, I honestly hadn't been aware of them but the problem stood out clearly in the graph.


2017-06-15

VERY USEFUL


2017-06-14

This really awesome tool, with just one click its providing very useful information


2017-06-13

Pretty sweet!


page 1 of 37  1 2 3 4 5 6 7 8 9 10Next