JDK-8192810 : EnableThreadSMRStatistics should be default off in release builds
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 10
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2017-11-30
  • Updated: 2017-12-15
  • Resolved: 2017-12-01
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.
JDK 10
10 b36Fixed
Related Reports
Relates :  
JDK-8192899 - EnableThreadSMRStatistics has some hot fields
Relates :  
JDK-8167108 - inconsistent handling of SR_lock can lead to crashes
Description
False sharing on the cacheline and adjacent cacheline causes 100% overhead in extreme benchmark.
The atomic inc by them self seem to cause ~1% overhead
Comments
If we split the EnableThreadSMRStatistics from the cache line issue, then yes. This bug can be used to change the default of EnableThreadSMRStatistics to 'trueInDebug'. We can have a different bug for looking at the cache line issue when EnableThreadSMRStatistics is enabled...
01-12-2017
[~dcubed], can this be fixed as a trivial change today? Else, please move to 11.
01-12-2017