Java 8 Garbage Collection Logging
External
Internal
Overview
Garbage collection logging is turned on by:
-verbose:gc
By default, the output is sent to stdout, and the format is somewhat limited:
[GC (Allocation Failure) 410112K->410112K(1048064K), 0.0010012 secs]
[Full GC (Allocation Failure) 410112K->512K(546304K), 0.0108077 secs]
The output can be sent into a configured file (including /dev/stdout), as shown here: Sending the GC Logging Output to a File.
The output format can be configured as shown here: Output Format Configuration.
Sending the GC Logging Output to a File
When -verbose:gc is used, the JVM sends the output to stdout. To configured it to send the output to a particular file, use:
-Xloggc:<file-path>
If -Xloggc option is used, the stdout output is not generated anymore, and the output is directed into the specified file. The file is created if does not exist, and if it exists, it is overwritten. The file path can be absolute or relative. In case of a relative path, it is relative to the current directory. "/dev/stdout" can be used as file name, in which case the output will be directed to stdout.
The option automatically turns on the following: -XX:+PrintGC, -XX:+PrintGCTimeStamps, so unlike in the case of the output produced by -verbose:gc, each entry is prefixed by the number of seconds and milliseconds since the JVM start:
169.963: [GC (Allocation Failure) 410112K->410112K(1048064K), 0.0008570 secs]
169.964: [Full GC (Allocation Failure) 410112K->512K(720896K), 0.0032239 secs]
-Xloggc also generates a few summary lines at the top of the file, including a JVM header line and the command line flags in effect:
Java HotSpot(TM) 64-Bit Server VM (25.221-b11) for bsd-amd64 JRE (1.8.0_221-b11), built on Jul 4 2019 04:36:22 by "java_re" with gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00)
Memory: 4k page, physical 33554432k(1243808k free)
/proc/meminfo:
CommandLine flags: -XX:InitialHeapSize=536870912 -XX:MaxHeapSize=1073741824 -XX:+PrintGC -XX:+PrintGCTimeStamps -XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:+UseParallelGC
0.710: [GC (Allocation Failure) 414863K->410120K(852480K), 0.0014617 secs]
0.712: [GC (Allocation Failure) 410120K->410072K(852480K), 0.0054436 secs]
...
Using -Xloggc makes the -verbose:gc option redundant, but it can be left on command line, as it will not cause any harm.
Output Format Configuration
The recommended GC logging configuration is:
-Xloggc:<absolute-path> -XX:+PrintGCDateStamps -XX:+PrintGCDetails
-XX:+PrintGC
-XX:+PrintGC
Enables printing of messages at every GC. -Xloggc:<file> turns this option on implicitly.
-XX:+PrintGCTimeStamps
-XX:+PrintGCTimeStamps
Enables printing of time stamps (time in seconds since the JVM started) at every GC. By default, this option is disabled. It is implicit turned on if -Xloggc:<file> is used. Time stamps recorded this way provide a chronology relative to the time the JVM started, but additional calculation is needed to translate the timestamps to normal timestamps, and it is only possible if the JVM start time is also recorded. A better way to record timestamps is to use -XX:+PrintGCDateStamps.
-XX:+PrintGCDateStamps
-XX:+PrintGCDateStamps
Records the GC event timestamps in the following format:
2017-02-12T19:26:03.328+0800:
-XX:+PrintGCDetails
Enables printing of detailed messages at every GC:
-XX:+PrintGCDetails
When used, each GC event contains information of how the event affected various heap areas such as the young generation, old generation and the metaspace. The default behavior is to report how the entire heap was modified as the result of the GC event. The difference in output is the following:
2017-02-12T19:26:03.378+0800: 0.144: [Full GC (Ergonomics) 126674K->126513K(413696K), 0.0181008 secs]
2017-02-12T19:42:35.003+0800: 0.156: [Full GC (Ergonomics) [PSYoungGen: 10721K->0K(141824K)] [ParOldGen: 115952K->126513K(270848K)] 126674K->126513K(412672K), [Metaspace: 3447K->3447K(1056768K)], 0.0182535 secs] [Times: user=0.10 sys=0.03, real=0.02 secs]
GC Log File Rotation
In case the space of the filesystem logs are written onto is limited, log rotation can be enabled as follows:
-XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles=5
-XX:GCLogFileSize=3M