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

Unify handling of thread sets when allocating them lazily

    XMLWordPrintable

Details

    • Enhancement
    • Status: Open
    • P4
    • Resolution: Unresolved
    • 10
    • tbd
    • hotspot
    • gc

    Description

      G1 and other collectors (parallel) use sets of threads as workers (e.g. gc workers, refinement, marking).

      Currently they are allocated upfront, except if -XX:+UseDynamicNumberOfGCThreads is used. In JDK-8190937 we would like to detach this lazy allocation from dynamically determining the number of gc threads.

      Before that is done, it may be prudent to think and unify the behavior in exceptional cases when lazy allocating them.

      Questions like:
      - what happens if we can't allocate a thread (during initialization, at the time of use)
      - is there a minimum number of threads in these sets that we absolutely need to operate?
      - warning messages if any, should they be repeated?

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated: