JDK-8185008 : Release Note: Change to Default Value for BiasedLockingStartupDelay
- Type: Sub-task
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 10
- Priority: P4
- Status: Closed
- Resolution: Delivered
- Submitted: 2017-07-20
- Updated: 2019-04-09
- Resolved: 2018-01-25
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 10 |
|---|
10Resolved  |
Description
The default value for `BiasedLockingStartupDelay` has been changed to 0. The flag `BiasedLockingStartupDelay` previously had the default value 4000 which delayed the use of biased locking with 4 s (4000 ms). The reason for this delay was performance but recent performance runs show no difference between the 4000 ms delay and no delay. Since having the delay will cause other parts of the VM to do extra work, having the default set to 0 makes more sense.