JDK-6492007 : tiered jvm is substantially slower on Alacrity client tests
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2006-11-09
  • Updated: 2010-12-08
  • Resolved: 2010-12-08
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 7
7Resolved
Related Reports
Duplicate :  
JDK-6953144 - Tiered compilation
Description
An alacrity run shows that the tiered jvm compares very unfavorably with the client jvm on client benchmarks. For example on sparc:

SwingMark -20%
SwingMark_Native -25%
JVM 98 -17%
startup3 -49%
 etc.

Results are similar on linux and windows.
Comments
EVALUATION At least some of this is because class data sharing is not supported with tiered compiler because of gc issues.
09-11-2006