GCViewer, garbage collection and heap analysis tool

Originally published January 12, 2009.
Information provided in this post may be out of date.

Jörg Wüthrich forked GCViewer in 2011 and has added support for Java 1.6 and 1.7 (including the new G1 collector). Tagtraum stopped improving its original version in 2008.

One month ago I wrote about the benefits of using Java’s built-in garbage collection logging.  With it, you can find answers to important important questions such as “how much memory is my app using” and “how much time is being spent doing garbage collection.”

There is, of course, a hitch: for any non-trivial application or problem, you will be quickly buried by a mountainous log file.  The longer your application runs, the larger the log file.  It keeps growing, and growing, and…

What will you do?  Write a second Java app, one that parses the log file – attempt a homegrown analysis tool?  No!  Instead, I suggest you use GCViewer, a free open-source tool for visualizing the Java gc log file.

GCViewer helps you get a quick and comprehensive look at how your application is behaving.  Things like total heap vs. heap used and full GC events become very apparent.  Useful statistics such as time spent during GC are calculated for your convenience.

GCViewer is a fork by Jörg Wüthrich and is available under an LGPL license.