This is a GC monitoring and management tool. It is specially designed to work closely with JVM Garbage Collector to provide an insight view into memory usage and effectiveness of garbage collector within a Java application.

Some of its features include:

1. It collects GC events and snapshot of memory usage information, and it works with many GC implementations such as CMS and G1.
2. Used as a JMX plug-in so application itself can receive real time update and alerts at runtime.
3. A history with configurable duration of GC events and memory utilization statistics.
4. Allow application log and GC log to the same file, or have the GC info stored into a different file, or sent to server

Benefit of using this tool:

1. Allow developer to understand GC behavior and effect it has on the application
• Determine memory size at startup, and max heap size
• Determine cost of GC (full GC) and the effect it has on application throughput

2. Combine application log and GC log together to ease debugging and troubling process
• This makes it easier to determine if the latency within an application is caused directly by a GC event.

3. Quantify cost in terms of memory consumption for each application task, so application throughput can be better measured and gauged.
• You can co-relate number of requests from client to the amount of memory consumed.
• Provide pointers for developer to look for new ways of optimization by focusing on memory consumption

4. Provide critical hints and tips for GC turning
• Historical memory usage and GC events gives developer information where the system tuning should have happened.
• Potential memory leak or objects are moved to old generation prematurely can be detected

5. Real-time alert of GC events to allow application to take proactive steps to reduce memory foot print, or seek other alternatives.
• Real-time GC notification is a strong indication and application should clean up memory or move the work load somewhere else
Please insert your text here.