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

    • gc
    • b07

        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.

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

                Created:
                Updated:
                Resolved: