G1: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
Line 92: Line 92:


The ''evacuation'' is the process of copying live objects from one G1 region to another. An "evacuation" collection is the most common type of young and mixed generation collection, where all the application threads are stopped and the GC system copies live objects across G1 regions.
The ''evacuation'' is the process of copying live objects from one G1 region to another. An "evacuation" collection is the most common type of young and mixed generation collection, where all the application threads are stopped and the GC system copies live objects across G1 regions.
=Configuration=
Enabled with:
<pre>
-X
</pre>
=TODO=
* Process http://www.oracle.com/technetwork/tutorials/tutorials-1876574.html

Revision as of 19:45, 19 April 2017

External

Internal

Overview

Evacuation is the process of copying live data from Young regions into Survivor regions (or free regions that thus become Survivors). During an Evacuation, all application threads are stopped.

Log marker:

[GC pause (G1 Evacuation Pause) (young), 0.7919126 secs]

Eden.


Spaces:

  • Young (or Eden)
  • Survivor
  • Old Generation


Metaspace

Process https://blogs.oracle.com/g1gc/entry/g1_gc_glossary_of_terms

Concepts

Collection

A collection gains the exclusive access of the heap and stops all application threads.

The collection can be "young", where only young and survivor regions are touched, or "mixed", where the collection includes young, survivor and old regions.

Collection Triggers

Allocation Failure

The main trigger for collection events, both young or mixed, is an object allocation failure. What does that mean? These collections are reported in the GC logs as "G1 Evacuation Pause":

2017-02-14T03:40:26.897-0600: 4.347: [GC pause (G1 Evacuation Pause) (young), 0.1014594 secs]
    ...

Metaspace Threshold Reached

A collection is triggered when metadata space usage reaches a threshold. This should not bee seen if ClassUnloadingWithConcurrentMark is enabled. These collections are reported in the GC logs as "Metadata GC Threshold":

2017-02-14T03:40:58.787-0600: 36.237: [GC pause (Metadata GC Threshold) (young) (initial-mark), 0.3979489 secs]
    ...

GCLocker Initiated GC

A collection is triggered when a JNI critical region was released. Garbage collection is blocked when any thread is in the JNI Critical region. If garbage collection was requested during that period, that garbage collection is invoked after all the threads come out of the JNI critical region.These collections are reported in the GC logs as "GCLocker Initiated GC":

2017-02-14T03:51:33.209-0600: 670.666: [GC pause (GCLocker Initiated GC) (young), 0.0326740 secs]
    ...

G1 Humongous Allocation

A collection is triggered when a humongous object allocation fails. These collections are reported in the GC logs as "G1 Humongous Allocation":

2017-02-14T04:02:06.690-0600: 1304.097: [GC pause (G1 Humongous Allocation) (young) (initial-mark), 0.0800982 secs]
    ...

Heap Dump

A full collection is triggered by a heap dump. These collections are reported in the GC logs as "Heap Dump Initiated GC".

System.gc()

A collection is triggered by a System.gc() call.

Evacuation

The evacuation is the process of copying live objects from one G1 region to another. An "evacuation" collection is the most common type of young and mixed generation collection, where all the application threads are stopped and the GC system copies live objects across G1 regions.

Configuration

Enabled with:

-X

TODO