Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Fixed
Priority: P4
Fix Version/s: 22
Affects Version/s: 9
Component/s: hotspot
Labels:

Subcomponent:
gc
Resolved In Build:
b10

A common case in evacuation failure is that only a very small subset of the original contents of the region experiencing the failure is live.
We mark the region as old and basically completely full.

This is a waste of space. A following GC could clean them out cheaply in many cases.

May also be very interesting in case of pinned regions, i.e. clean the affected regions out in the next gc.

is blocked by

JDK-8306920 G1: Calculate garbage bytes for evacuation failed regions from marked live bytes

Closed

relates to

JDK-8314157 G1: "yielded" is not initialized on some paths after JDK-8140326

Resolved

JDK-8315501 G1: Do not require marking region evacuation in Prepare Mixed GC

Closed

JDK-8300770 G1: Allow optional code root memregions

Open

JDK-8314884 G1: Exclude eager reclaim candidates from marking

Open

JDK-8306541 Refactor collection set candidate handling to prepare for JDK-8140326

Resolved

JDK-8315686 G1: Disallow evacuation of marking regions in a Prepare Mixed gc

Resolved

JDK-7162317 G1: Explicitly mark self-forwarded objects during marking cycles

Closed

JDK-8315502 G1: Abort mixed phase if Prepare Mixed cleaned out all marking regions

Closed

JDK-8251288 G1: Young gen sizing should take short-living humongous object allocation into account

Closed

JDK-8276094 JEP 423: Region Pinning for G1

Closed

links to

Commit openjdk/jdk/7e209528

Review openjdk/jdk/14220

(6 relates to, 2 links to)

Release Note: G1: Fast Collection of Evacuation Failed Regions

Resolved

Thomas Schatzl

Assignee:: Thomas Schatzl

Reporter:: Thomas Schatzl

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2015-10-22 05:42

Updated:: 2023-09-05 04:33

Resolved:: 2023-08-08 03:31

Details

Description

Attachments

Issue Links

Sub-Tasks

Activity

People

Dates