eG Help

Manual memory management is time consuming, and error prone. Most programs still contain leaks. This is all doubly true with programs using exception-handling and/or threads. Garbage collection (GC) is a part of Tomcat's JVM that automatically determines what memory a program is no longer using, and recycles it for other use. It is also known as "automatic storage (or memory) reclamation''. The JVMGarbageTest reports the performance statistics pertaining to the JVM's garbage collection.

Measurement	Description	Measurement Unit	Interpretation
No_of_collections	Indicates the number of garbage collections that were performed by the JVM since the last measurement period	Number	If adequate memory is not allotted to the JVM, then the value of this measure would be very high. A high value of this measure is indicative of a high frequency of GC. This is not a good sign, as GC, during its execution, has the tendency of reducing the performance for applications, and a high frequency of GC would only adversely impact the application's performance. To avoid this, it is recommended that you allot sufficient memory to the JVM.
Time_taken	Indicates the time taken for GC execution, since the last measurement period	Secs	A shorter GC execution time is desired to avoid issues in application performance and database connection bottlenecks.
Elapsed_time	Indicates the percentage of time spent on GC execution	Percent	By carefully examining the application behavior in terms of memory utilization, you should arrive at an optimal ratio of the number of times the GC needs to run and how long it should take to complete. Accordingly, you can fine-tune the GC activity.