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

G1: Handling objects that fail evacuation very slow

    XMLWordPrintable

    Details

    • Subcomponent:
      gc

      Description

      Some measurements with specjbb2015 fixed ir=6000, 16gb heap and inducing evacuation failures using G1EvacuationFailureALot (everything else related normal) shows that evacuation failures lengthen the "Object Copy" phase a lot.

      See the attached graph that shows "Object Copy" time for evacuation failures and without within that run.

      With object pinning we need this to be almost as fast, so investigate what could be done here.

      Some ideas:
        * move out absolutely unnecessary code from object copy, ie. statistics gathering for JFR; could be done when removing the self-forwards, or in an extra stage later (i.e. recording all object sizes and do the statistics separately in parallel)
        * potentially always record preserved marks for failed objects; checking whether it is actually required may be more costly than just doing that all the time (would somewhat work together with JDK-8254739)
        * maybe other suggested changes (splitting processing "large" objects, JDK-8271870) helps because this is a work distribution problem in the end
        * avoid the constant lookup of various data via the HeapRegion* pointer; we have the G1HeapRegionAttr available
        * usual micro-optimizations like look for code duplication along the call chain

      Of course, first analyze what is responsible for the slowdown.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mli Hamlin Li
              Reporter:
              tschatzl Thomas Schatzl
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: