JDK-8026423 : PSR: Perf JMS benchmark regression compared to JRockit
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 7u1
  • Priority: P2
  • Status: Resolved
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2013-10-14
  • Updated: 2015-08-19
  • Resolved: 2015-08-19
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 9
9Resolved
Related Reports
Duplicate :  
JDK-8046133 - JEP 143: Improve Contended Locking
Relates :  
JDK-8049158 - Improve Contended Locking Development
Relates :  
JDK-8046133 - JEP 143: Improve Contended Locking
Relates :  
JDK-7117065 - RFE: Improve contended locking support
Description
See Comments
Comments
A majority of Dave Dice's locking improvements have been integrated in various JDK9 builds using the following JEP: JDK-8046133 JEP 143: Improve Contended Locking For the details on which bucket of changes went into which JDK9 build, see: JDK-8049158 Improve Contended Locking Development I'm planning to close this bug as a duplicate of JDK-8046133.
19-08-2015
According to the bugdb report this issue is due to lock contention. The performance issue has been reported to be fixed by applying some patch to locking internals. Locking seems to be the responsibility of the runtime team, changed the subcomponent accordingly.
16-10-2013