Is there a measurable performance difference here? I'd be willing to
do anything that improved performance, presuming that it was not
completely onerous to write code or use it.
What is the alternative to autoboxing?
On Jul 15, 2009, at 2:02 PM, Stephane wrote:
I am looking at Thrift for some project and I have noticed that the
java
code generated by thriftc is relying on the Java VM for
autoboxing... I am
in some way surprise to find many spots where it's happening, and
at first
my Eclipse project was not compiling since for performance reason
my default
project settings were to generate a compilation error when detecting
autoboxing.
Is there any plan in the future to avoid autoboxing and rather
generate some
java code that do not have the -small- penalty of getting the VM do
the
extra work ? I know the cost is small but any performance gain
should be
considered no ?
Stéphane
