JDK-8150629 : Initializing all ParScanThreadStates causes significant unaccounted "Other" times
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2016-02-25
- Updated: 2018-06-21
- Resolved: 2016-02-26
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.
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.
| JDK 9 |
|---|
9 b110Fixed  |
Related Reports
|
Relates :
|
Description
Applications with many regions in the cset (large young gen) and many threads show that there is a significant amount of unaccounted "Other" times. One part of this is caused by initializing and merging the information in all ParScanThreadStates for all threads in the VM pause. This CR is about fixing the initialization by moving the ParScanThreadState initialization into the worker threads. The PSS merge phase is covered by JDK-8150239.