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

G1: Full gc mark stack draining should prefer to make work available to other threads

    XMLWordPrintable

Details

    • Enhancement
    • Status: Resolved
    • P4
    • Resolution: Fixed
    • 19
    • 19
    • hotspot
    • gc
    • b07

    Description

      G1 full gc marking currently does not preferentially move overflow stack contents to make work available to other threads.

      I.e. if there is a single thread having work in its overflow stack, it tries to work on that one by itself; other threads that steal that have nothing to do as the stack to steal from is kind of empty.

      On BRT 20gb, in the initial full gcs to compact the heap, changing this saves 400ms of 1500ms total pause time.

      This is a similar problem G1 young gc showed long time ago.

      Attachments

        Issue Links

          relates to

          Enhancement - null JDK-8156754 Encapsulate task queue policies into queue/task specific classes to use

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

          Enhancement - null JDK-8152438 Threads may do significant work out of the non-shared overflow buffer

          • P3 - Major loss of function.
          • Resolved

          Enhancement - null JDK-8280958 G1/Parallel: Unify marking code structure

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

          Enhancement - null JDK-8280705 Parallel: Full gc mark stack draining should prefer to make work available to other threads

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

          Commit Commit openjdk/jdk/674a97b2

          Review Review openjdk/jdk/7175

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: