Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Unresolved
Priority: P4
Fix Version/s: tbd
Affects Version/s: 14
Component/s: hotspot
Labels:
- g1-humongous
- gc-g1

Subcomponent:
gc

One idea to sidestep the humongous object fragmentation issue in G1 could be reserving a multiple of MaxHeapSize for the G1 java heap and make sure that G1 only ever commits MaxHeapsize space.

The feature to allow allocation of the old gen on NV-DIMM in ~~JDK-8202286~~ implemented a similar scheme.

Azul's Zing also does the same.

blocks

JDK-8251263 G1: Only commit actually used space for humongous objects

Open

relates to

JDK-8229049 JEP 363: Remove the Concurrent Mark Sweep (CMS) Garbage Collector

Closed

JDK-8030849 Investigate high fragmentation/waste in some situations during allocation during GC in G1

Open

JDK-8202286 Allocation of old generation of Java heap on alternate memory devices

Resolved

Assignee:: Unassigned

Reporter:: Thomas Schatzl

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2019-08-09 08:19

Updated:: 2020-08-06 11:24

Details

Description

Attachments

Issue Links

Activity

People

Dates