JDK-8140326 : G1: Consider putting regions where evacuation failed into next collection set
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2015-10-22
  • Updated: 2023-09-05
  • Resolved: 2023-08-08
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 22
22 b10Fixed
Related Reports
Blocks :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Description
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.

Comments
Changeset: 7e209528 Author: Thomas Schatzl <tschatzl@openjdk.org> Date: 2023-08-08 10:29:14 +0000 URL: https://git.openjdk.org/jdk/commit/7e209528d3690ff25f00efaa60bc10fadfb2c010
08-08-2023

A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/14220 Date: 2023-05-30 14:00:30 +0000
31-05-2023

JDK-7162317 is an idea for special case handling for evac failure during marking.
18-05-2020