Symbolic benchmark

[Lew]

As far as I know that optimisation hasn't been implemented in HotSpot
yet. It is planned.

The accessor calls are inlined, but the object creation remains.

immutable objects where == is a value comparison can be placed directly
in arrays instead of arrays of references. This is important in many
applications of complex values.

Mark Thornton

 

[Lew]

The accessor calls are inlined, but the object creation remains.

According to Sun, they've expanded this capability already in Java 6, at least
if I understand
<http://java.sun.com/performance/reference/whitepapers/6_performance.html#2.1.7>
correctly.

Sun references
<http://www.ssw.uni-linz.ac.at/Research/Papers/Ko05/>
and
<http://www.ssw.uni-linz.ac.at/Research/Papers/Wimmer04Master/>
in the context of the latest HotSpot VM.

Also,
<http://developers.sun.com/learning/....jsp?sessn=TS-3412&yr=2006&track=coreplatform>

particularly pp. 24-42.

 

[Mark Thornton]

According to Sun, they've expanded this capability already in Java 6, at
least if I understand
<http://java.sun.com/performance/reference/whitepapers/6_performance.html#2.1.7>

correctly.

My understanding is that the use of escape analysis for synchronization
optimization made the cut into Java 6, but the use for eliminating
object allocation did not. Much of the development had been done, but it
wasn't considered ready in time.

Mark Thornton

 

[Lew]

My understanding is that the use of escape analysis for synchronization
optimization made the cut into Java 6, but the use for eliminating
object allocation did not. Much of the development had been done, but it
wasn't considered ready in time.

Undoubtedly your information is better than mine.

I can hardly wait.