G1垃圾回收器

G1垃圾回收器重要参数

The Garbage First Garbage Collector (G1 GC) is the low-pause, server-style generational garbage collector for Java HotSpot VM. The G1 GC uses concurrent and parallel phases to achieve its target pause time and to maintain good throughput. When G1 GC determines that a garbage collection is necessary, it collects the regions with the least live data first (garbage first).

前言

A garbage collector (GC) is a memory management tool. The G1 GC achieves automatic memory management through the following operations:

Allocating objects to a young generation and promoting aged objects into an old generation.
Finding live objects in the old generation through a concurrent (parallel) marking phase. The Java HotSpot VM triggers the marking phase when the total Java heap occupancy exceeds the default threshold.
Recovering free memory by compacting live objects through parallel copying.

G1介绍

Here, we look at how to adapt and tune the G1 GC for evaluation, analysis and performance—we assume a basic understanding of Java garbage collection.

The G1 GC is a regionalized and generational garbage collector, which means that the Java object heap (heap) is divided into a number of equally sized regions. Upon startup, the Java Virtual Machine (JVM) sets the region size. The region sizes can vary from 1 MB to 32 MB depending on the heap size. The goal is to have no more than 2048 regions. The eden, survivor, and old generations are logical sets of these regions and are not contiguous.

The G1 GC has a pause time-target that it tries to meet (soft real time). During young collections, the G1 GC adjusts its young generation (eden and survivor sizes) to meet the soft real-time target. During mixed collections, the G1 GC adjusts the number of old regions that are collected based on a target number of mixed garbage collections, the percentage of live objects in each region of the heap, and the overall acceptable heap waste percentage.

The G1 GC reduces heap fragmentation by incremental parallel copying of live objects from one or more sets of regions (called Collection Set (CSet)) into different new region(s) to achieve compaction. The goal is to reclaim as much heap space as possible, starting with those regions that contain the most reclaimable space, while attempting to not exceed the pause time goal (garbage first).

The G1 GC uses independent Remembered Sets (RSets) to track references into regions. Independent RSets enable parallel and independent collection of regions because only a region’s RSet must be scanned for references into that region, instead of the whole heap. The G1 GC uses a post-write barrier to record changes to the heap and update the RSets.

回收原理

Garbage Collection Phases
Apart from evacuation pauses (described below) that compose the stop-the-world (STW) young and mixed garbage collections, the G1 GC also has parallel, concurrent, and multiphase marking cycles. G1 GC uses the Snapshot-At-The-Beginning (SATB) algorithm, which takes a snapshot of the set of live objects in the heap at the start of a marking cycle. The set of live objects is composed of the live objects in the snapshot, and the objects allocated since the start of the marking cycle. The G1 GC marking algorithm uses a pre-write barrier to record and mark objects that are part of the logical snapshot.

Young Garbage Collections
The G1 GC satisfies most allocation requests from regions added to the eden set of regions. During a young garbage collection, the G1 GC collects both the eden regions and the survivor regions from the previous garbage collection. The live objects from the eden and survivor regions are copied, or evacuated, to a new set of regions. The destination region for a particular object depends upon the object’s age; an object that has aged sufficiently evacuates to an old generation region (that is, promoted); otherwise, the object evacuates to a survivor region and will be included in the CSet of the next young or mixed garbage collection.

Mixed Garbage Collections
Upon successful completion of a concurrent marking cycle, the G1 GC switches from performing young garbage collections to performing mixed garbage collections. In a mixed garbage collection, the G1 GC optionally adds some old regions to the set of eden and survivor regions that will be collected. The exact number of old regions added is controlled by a number of flags that will be discussed later (see “Taming Mixed GCs”). After the G1 GC collects a sufficient number of old regions (over multiple mixed garbage collections), G1 reverts to performing young garbage collections until the next marking cycle completes.

Phases of the Marking Cycle
The marking cycle has the following phases:

• Root region scanning phase: The G1 GC scans survivor regions of the initial mark for references to the old generation and marks the referenced objects. This phase runs concurrently with the application (not STW) and must complete before the next STW young garbage collection can start.
• Concurrent marking phase: The G1 GC finds reachable (live) objects across the entire heap. This phase happens concurrently with the application, and can be interrupted by STW young garbage collections.
• Remark phase: This phase is STW collection and helps the completion of the marking cycle. G1 GC drains SATB buffers, traces unvisited live objects, and performs reference processing.
• Cleanup phase: In this final phase, the G1 GC performs the STW operations of accounting and RSet scrubbing. During accounting, the G1 GC identifies completely free regions and mixed garbage collection candidates. The cleanup phase is partly concurrent when it resets and returns the empty regions to the free list.

Important Defaults

G1 GC 是一个自适应垃圾回收器，具有默认值，使其无需修改即可高效工作。以下是重要选项及其默认值的列表。此列表适用于最新的 Java 热点 VM，内部版本 24。通过在 JVM 命令行上输入以下选项并更改了设置，您可以根据应用程序性能需求调整和调整 G1 GC。

-XX:G1HeapRegionSize=n
Sets the size of a G1 region. The value will be a power of two and can range from 1MB to 32MB. The goal is to have around 2048 regions based on the minimum Java heap size.(设置 G1 region的大小。该值将是 2 的幂，范围从 1MB 到 32MB。目标是根据最小的 Java 堆大小拥有大约 2048 个区域。)

-XX:MaxGCPauseMillis=200
Sets a target value for desired maximum pause time. The default value is 200 milliseconds. The specified value does not adapt to your heap size.(为所需的最大暂停时间设置目标值。默认值为 200 毫秒。指定的值不适应您的堆大小。)

-XX:G1NewSizePercent=5
Sets the percentage of the heap to use as the minimum for the young generation size. The default value is 5 percent of your Java heap. This is an experimental flag. See “How to unlock experimental VM flags” for an example. This setting replaces the -XX:DefaultMinNewGenPercent setting. This setting is not available in Java HotSpot VM, build 23.(设置要用作年轻一代大小的最小值的堆的百分比。缺省值为 Java 堆的 5%。这是一个实验性标志。有关示例，请参阅“如何解锁实验性 VM 标志”。此设置将替换“-XX：默认明新一代”设置。此设置在 Java 热点 VM 内部版本 23 中不可用。)

-XX:G1MaxNewSizePercent=60
Sets the percentage of the heap size to use as the maximum for young generation size. The default value is 60 percent of your Java heap. This is an experimental flag. See “How to unlock experimental VM flags” for an example. This setting replaces the -XX:DefaultMaxNewGenPercent setting. This setting is not available in Java HotSpot VM, build 23.(设置要用作年轻一代大小的最大值的堆大小的百分比。缺省值为 Java 堆的 60%。这是一个实验性标志。有关示例，请参阅“如何解锁实验性 VM 标志”。此设置将替换“-XX：默认值”新建“设置。此设置在 Java 热点 VM 内部版本 23 中不可用。)

-XX:ParallelGCThreads=n
Sets the value of the STW worker threads. Sets the value of n to the number of logical processors. The value of n is the same as the number of logical processors up to a value of 8.(设置 STW 工作线程的值。将 n 的值设置为逻辑处理器的数目。n 的值与逻辑处理器的数量相同，最大值为 8。)

If there are more than eight logical processors, sets the value of n to approximately 5/8 of the logical processors. This works in most cases except for larger SPARC systems where the value of n can be approximately 5/16 of the logical processors.(如果逻辑处理器超过 8 个，请将 n 的值设置为大约 5/8 的逻辑处理器。这在大多数情况下都有效，但较大的 SPARC 系统除外，其中 n 的值可以大约是逻辑处理器的 5/16。)

-XX:ConcGCThreads=n
Sets the number of parallel marking threads. Sets n to approximately 1/4 of the number of parallel garbage collection threads (ParallelGCThreads).
(设置并行标记螺纹的数量。将 n 设置为大约并行垃圾回收线程数（并行 GC 线程数）的 1/4.)

-XX:InitiatingHeapOccupancyPercent=45
Sets the Java heap occupancy threshold that triggers a marking cycle. The default occupancy is 45 percent of the entire Java heap.(设置触发标记周期的 Java 堆占用阈值。缺省占用率是整个 Java 堆的 45%。)

-XX:G1MixedGCLiveThresholdPercent=65
Sets the occupancy threshold for an old region to be included in a mixed garbage collection cycle. The default occupancy is 65 percent. This is an experimental flag. See “How to unlock experimental VM flags” for an example. This setting replaces the -XX:G1OldCSetRegionLiveThresholdPercent setting. This setting is not available in Java HotSpot VM, build 23.(设置要包含在混合垃圾回收周期中的旧区域的占用阈值。默认占用率为 65%。这是一个实验性标志。有关示例，请参阅“如何解锁实验性 VM 标志”。此设置将替换 -XX：G1OldCSet区域生存阈值百分比设置。此设置在 Java 热点 VM 内部版本 23 中不可用。)

-XX:G1HeapWastePercent=10
Sets the percentage of heap that you are willing to waste. The Java HotSpot VM does not initiate the mixed garbage collection cycle when the reclaimable percentage is less than the heap waste percentage. The default is 10 percent. This setting is not available in Java HotSpot VM, build 23.

-XX:G1MixedGCCountTarget=8
Sets the target number of mixed garbage collections after a marking cycle to collect old regions with at most G1MixedGCLIveThresholdPercent live data. The default is 8 mixed garbage collections. The goal for mixed collections is to be within this target number. This setting is not available in Java HotSpot VM, build 23.(设置您愿意浪费的堆的百分比。当可回收百分比小于堆浪费百分比时，Java 热点 VM 不会启动混合垃圾回收周期。默认值为 10%。此设置在 Java 热点 VM 内部版本 23 中不可用。)

-XX:G1OldCSetRegionThresholdPercent=10
Sets an upper limit on the number of old regions to be collected during a mixed garbage collection cycle. The default is 10 percent of the Java heap. This setting is not available in Java HotSpot VM, build 23.(设置混合垃圾回收周期期间要收集的旧区域数的上限。缺省值为 Java 堆的 10%。此设置在 Java 热点 VM 内部版本 23 中不可用。)

-XX:G1ReservePercent=10
Sets the percentage of reserve memory to keep free so as to reduce the risk of to-space overflows. The default is 10 percent. When you increase or decrease the percentage, make sure to adjust the total Java heap by the same amount. This setting is not available in Java HotSpot VM, build 23.(设置保留内存的百分比以保持可用，以降低空间溢出的风险。默认值为 10%。增加或减少百分比时，请确保按相同的量调整总 Java 堆。此设置在 Java 热点 VM 内部版本 23 中不可用。)
一个具有注脚的文本。¹

---

1. 参考：https://www.oracle.com/technical-resources/articles/java/g1gc.html ↩︎