Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8306696

Remove MetaspaceReclaimPolicy=aggressive and obsolete MetaspaceReclaimPolicy

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Fixed
    • P4
    • 21
    • 21
    • hotspot
    • b21

    Description

      The diagnostic setting MetaspaceReclaimPolicy=aggressive is very rarely used, and I would like to remove it. This is a part of a larger effort to simplify metaspace coding and cut down on testing time, in preparation for upcoming changes to Metaspace with Lilliput.

      MetaspaceReclaimPolicy had recently been demoted from an official to a diagnostic switch (see CSR JDK-8302130). See also the CSR text for a more in-depth explanation of what this switch does, its history, and why it could be removed for good.

      The switch has not that much impact on RSS reduction but has the side effect of increasing VMA fragmentation compared to the default setting since it reduces the size of metaspace commit granules from 64K to 16K. The settings used by default (MetaspaceReclaimPolicy=balanced) are proven now in the field and can be used without alternatives (since any alternative has to be tested).

      Since this would remove the last valid value for MetaspaceReclaimPolicy apart from its default "balanced" value, it makes sense to obsolete MetaspaceReclaimPolicy at the same time.

      This allows us to cut down on Metaspace testing quite a bit since it removes one permutation from the test set.


      Attachments

        Issue Links

          Activity

            People

              stuefe Thomas Stuefe
              stuefe Thomas Stuefe
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: