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
    • Status: Open
    • P4
    • Resolution: Unresolved
    • 14
    • tbd
    • 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

          blocks

          Enhancement - null JDK-8251263 G1: Only commit actually used space for humongous objects

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Open
          relates to

          JEP - Java Enhancement Proposal JDK-8229049 JEP 363: Remove the Concurrent Mark Sweep (CMS) Garbage Collector

          • P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Enhancement - null JDK-8030849 Investigate high fragmentation/waste in some situations during allocation during GC in G1

          • P3 - Major loss of function.
          • Open

          Enhancement - null JDK-8202286 Allocation of old generation of Java heap on alternate memory devices

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

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

              Dates

                Created:
                Updated: