devxlogo

Monitoring Garbage Collection in the JVM

Monitoring Garbage Collection in the JVM

Big applications create huge numbers of objects. Though Java manages the memory allocation and de-allocation for these objects, sometimes this huge number can result in memory leak problem. To monitor when and how much garbage collection is happening, use the following example method:

  1. Suppose you start your application as:
    java MyMainClass option1 option2.....
  2. To determine when garbage collection is happening, start your application as:
    java -verbose:gc MyMainClass option1 option2.....
  3. If garbage collection takes place, your output should show something like this:
    [GC 511K->105K(1984K), 0.0029585 secs]

The numbers before and after the arrow indicate the combined size of live objects before and after garbage collection. The number in parenthesis is the total available space, which is the total heap minus one of the survivor spaces.

Note: Remember that the figures in the output depend on your application and JVM.

devxblackblue

About Our Editorial Process

At DevX, we’re dedicated to tech entrepreneurship. Our team closely follows industry shifts, new products, AI breakthroughs, technology trends, and funding announcements. Articles undergo thorough editing to ensure accuracy and clarity, reflecting DevX’s style and supporting entrepreneurs in the tech sphere.

See our full editorial policy.

About Our Journalist