IBM®
Skip to main content
    United States change      Terms of use
 
 
Select a scope:    
     Home      Products      Services & industry solutions      Support & downloads      My account     
alphaWorks  >  Java technology  >  

IBM Pattern Modeling and Analysis Tool for Java Garbage Collector

A tool that parses verbose GC trace, analyzes Java heap usage, and recommends key configurations based on pattern modeling of Java heap usage.


Date Posted: April 12, 2005
Overview Requirements DownloadFAQsForum Reviews

1. What does an IBM® verbose GC trace look like?


1. What does an IBM® verbose GC trace look like?

An IBM verbose GC trace typically looks like this:

<AF[1]: Allocation Failure. need 1544 bytes, 0 ms since last AF>

<AF[1]: managing allocation failure, action=1 (0/3983128) (209640/209640)>

<GC(1): GC cycle started Tue Apr 24 10:49:58 2001>

<GC(1): freed 1421672 bytes, 38% free (1631312/4192768), in 9 ms>

<GC(1): mark: 8 ms, sweep: 1 ms, compact: 0 ms>

<GC(1): refs: soft 0 (age >= 32), weak 17, final 16, phantom 0>

<AF[1]: completed in 10 ms>

Notes:

  • GC(1): The 1st garbage collection cycle in this JVM (Java™ virtual machine).
  • freed 1,421,672 bytes: An indication of the amount of activity since the last garbage collection cycle.


Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
IBM is a trademark of IBM Corporation in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.

Back to top Back to top
View screenshots:
Overview screen of a

Download now Download now

Related technologies

For platform(s):
Java

For topics:
analysis, garbage collection, Java technology, modeling, Parsers, performance, trace, visualization


Related resources

Visualization Research topic

 

    About IBM Privacy Contact