Developers take advantage of the JVM argument -XX:+UseGCLogFileRotation to rotate GC log files.
Example:
Try to Avoid -XX:+UseGCLogFileRotation
What Are Garbage Collection Logs, Thread Dumps, and Heap Dumps?
Java Virtual Machine (JVM) generates 3 critical artifacts that are useful for optimizing the performance and troubleshooting production problems. Those artifacts are:
- Garbage collection (GC) log
- Thread Dump
- Heap Dump
In this article, let's try to understand these 3 critical artifacts, where to use them, how do they look, how to capture them, how to analyze them, and their differences.
7 JVM Arguments of Highly Effective Applications
At the time (March 2020) of writing this article, there are 600+ arguments that you can pass to JVM just around garbage collection and memory. If you include other aspects, the number of JVM arguments will easily cross 1000+. It’s way too many arguments for anyone to digest and comprehend. In this article, we will highlight seven important JVM arguments that you may find useful.
1. -Xmx and -XX:MaxMetaspaceSize
-Xmx is probably the most important JVM argument. -Xmx defines the maximum amount of heap size you are allocating to your application. (To learn about different memory regions in a JVM, you may watch this short video clip). You can define your application’s heap size like this: