-
Enhancement
-
Resolution: Done
-
Blocker
-
None
-
None
Setting MaxMetaspaceSize is generally not recommended, so we should stop doing it. If our OOTB setting is too low, users can experience unnecessary OOMEs.
https://access.redhat.com/solutions/1489263
Note: This is not about removing the setting of MetaspaceSize. Setting that can't cause an OOME and has a very small beneficial impact on boot time. (One measurement had it at 17ms, which is in the 0.5%-1% range of the total empty server boot.) I'll file a separate lower priority issue for removing MetaspaceSize; work on this issue should not block on that.
- blocks
-
JBEAP-24746 Remove Metaspace options
- Resolved
- is cloned by
-
WFLY-19940 Remove MaxMetaspaceSize settings
- Resolved
- relates to
-
WFCORE-7050 Remove MetaspaceSize settings
- Resolved