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

Reserve more than MaxHeapSize for the heap to fight humongous object fragmentation in G1

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Unresolved
    • P4
    • tbd
    • 14
    • hotspot
    • gc

    Description

      One idea to sidestep the humongous object fragmentation issue in G1 could be reserving a multiple of MaxHeapSize for the G1 java heap and make sure that G1 only ever commits MaxHeapsize space.

      The feature to allow allocation of the old gen on NV-DIMM in JDK-8202286 implemented a similar scheme.

      Azul's Zing also does the same.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              tschatzl Thomas Schatzl
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: