JDK-8191082 : Unify handling of thread sets when allocating them lazily
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 10
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2017-11-10
  • Updated: 2019-02-11
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8190937 - Always lazily allocate threads in G1
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?