JEP 318: Epsilon: No-Op Garbage Collector - remove 'Experimental' status

[Eelco de Vlieger]

Hello,
Not sure if this is the right place to ask this question.

`JEP 318: Epsilon: A No-Op Garbage Collector` (https://openjdk.org/jeps/318)
has been included since OpenJDK Release 11.

`-XX:+UseEpsilonGC` activates this (no-op) GC implementation, but only if
`-XX:+UnlockExperimentalVMOptions` is also provided.

Three of the stated use-cases in the JEP can be classed as production
(non-testing) functionality:
- Last-drop latency improvements for ultra-latency-sensitive applications
- Last-drop throughput improvements
- Extremely short lived jobs

After being included in 10 major java releases, is it not time to remove
the 'Experimental' status on the Epsilon garbage collector and related VM
options?

Kind regards,
Eelco

VM Options Explorer (https://chriswhocodes.com/vm-options-explorer.html)
search for 'Epsilon' lists:
 - UseEpsilonGC
 - EpsilonElasticTLAB
 - EpsilonElasticTLABDecay
 - EpsilonMaxTLABSize
 - EpsilonMinHeapExpand
 - EpsilonPrintHeapSteps
 - EpsilonTLABDecayTime
 - EpsilonTLABElasticity
 - EpsilonUpdateCountersStep
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20240105/c80f98ce/attachment.htm>