JDK-8015107 : NPG: Use consistent naming for metaspace concepts
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: hs25
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2013-05-22
  • Updated: 2017-05-17
  • Resolved: 2013-09-10
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8 Other
8Fixed hs25Fixed
Description
The naming for metaspace should be:
- CompressKlassSpace for the additonal space that is used when compressed klass pointers are used
- Metaspace for either:
  a) All metadata if compressed klass pointers *are not* used
  b) All metadata except klass metadata if compressed klass pointers *are* used

To enforce this, the VM flag  -XX:ClassMetaspaceSize must be renamed to -XX:CompressedClassSpaceSize and the documentation for the flags -XX:MaxMetaspaceSize and -XX:MetaspaceSize must be updated.

The flag -XX:CompressedClassSpaceSize is the size used for klass metadata when compressed class pointers are used. If compressed class pointers are not used, then the usage of -XX:CompressedClassSpaceSize will generate a warning.

If compressed class pointers are not used, then the flags -XX:MaxMetaspaceSize and -XX:MetaspaceSize will cover all of metadata (including the one for classes). If compressed class pointers are used, then -XX:MaxMetaspaceSize and -XX:MetaspaceSize will cover all metadata except the metadata used for classes (which then is covered by -XX:CompressedClassSpaceSize).