Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Fixed
Priority: P4
Fix Version/s: 23
Affects Version/s: 21, 22, repo-shenandoah
Component/s: hotspot
Labels:

Subcomponent:
gc
Resolved In Build:
b03

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8324984	22.0.1	William Kemper	P4	Resolved	Fixed	b03
JDK-8328108	21.0.4	William Kemper	P4	Resolved	Fixed	b01
JDK-8324982	17.0.11	William Kemper	P4	Resolved	Fixed	b01

Presently, every change to the gc change is distributed to all java threads. The gc state is only changed on safepoints. For applications with a very large number of java threads this may increase time on the safepoint. It would be better to synchronize the gc state only once per safepoint.

backported by

JDK-8324982 Shenandoah: gc state should be synchronized to java threads only once per safepoint

Resolved

JDK-8324984 Shenandoah: gc state should be synchronized to java threads only once per safepoint

Resolved

JDK-8328108 Shenandoah: gc state should be synchronized to java threads only once per safepoint

Resolved

relates to

JDK-8322503 Shenandoah: Clarify gc state usage

Resolved

links to

Commit openjdk/jdk17u-dev/5e8883e5

Commit openjdk/jdk21u-dev/ad5a0878

Commit openjdk/jdk22u/dfc86f9f

Commit openjdk/jdk/808a0392

Review openjdk/jdk17u-dev/2177

Review openjdk/jdk21u-dev/217

Review openjdk/jdk22u/31

Review openjdk/jdk/17112

(7 links to)

Assignee:: William Kemper

Reporter:: William Kemper

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2023-12-11 11:49

Updated:: 2024-03-13 09:13

Resolved:: 2023-12-18 16:11

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates