-
Enhancement
-
Resolution: Fixed
-
P4
-
21
-
b11
Metaspace, since JEP-387, reclaims memory after purging and returns it to the Operating System. We added a MetaspaceReclaimPolicy switch to control this behavior. Among other things, we allow reclamation to be completely disabled (MetaspaceReclaimPolicy=none). This was a fallback mechanism in case the JEP-387 metaspace turned out buggy.
But post-JEP-387 metaspace is pretty stable, and has been in the OpenJDK since Java 16, so this reclaim mode is not needed (see also CSRJDK-8302130).
This mode makes backend coding and test coding more complex, since arguing about how much memory we expect metaspace to have committed is difficult if we don't reclaim. Removing this mode would remove some of that complexity.
But post-JEP-387 metaspace is pretty stable, and has been in the OpenJDK since Java 16, so this reclaim mode is not needed (see also CSR
This mode makes backend coding and test coding more complex, since arguing about how much memory we expect metaspace to have committed is difficult if we don't reclaim. Removing this mode would remove some of that complexity.
- relates to
-
JDK-8302708 Release Note: The `MetaspaceReclaimPolicy` Flag has Been Obsoleted
-
- Resolved
-
-
-
- Resolved
-
-
JDK-8302625 Bad copyright line after JDK-8302385
-
- Resolved
-
-
JDK-8221173 JEP 387: Elastic Metaspace
-
- Closed
-
-
JDK-8302130 Make MetaspaceReclaimPolicy a diagnostic switch
-
- Closed
-
(2 links to)
There are no Sub-Tasks for this issue.