Use parallel garbage collection for scavenges. Following are a few JVM arguments which can be used to tune the garbage collection process: This can be achieved through a number of JVM arguments. The garbage collection process can be tuned for different applications based on the object creation characteristics of the application. Garbage collection will free up the memory of an object that doesn’t have any reference it will destroy unused objects. In C++, memory can be released manually, but it will happen automatically in Java using a process called garbage collection. One of the advantages of Java over C++ is automatic memory management. 64MB is the maximum heap size by default. If any application requires more than 2 GB, it should run on 64 bit JVM. The maximum heap size that can be configured in a 32 bit JVM is 2GB. The heap space can be configured using the following JVM arguments: The space used by the Java Runtime to allocate memory to Objects and JRE Classes is called Heap. Before going to the details, we will discuss the following points: The purpose of this article is to explain the use of a heap analyzer tool to identify a memory leakage in larger enterprise Java applications, which use a larger size of heaps.

It may occur only in production after running for a long time. Identifying the reason for an OutOfMemory error in Java applications with a larger heap size is a nightmare for a developer, because most of the OutOfMemory situations may not be identified during the testing phase.

How to use eclipse memory analyzer