Posted by Michael Bien on Mar 04, 2011; 3:38pm
URL: https://forum.jogamp.org/Change-JogAmp-Module-s-Java-Language-Version-Constraints-tp2448646p2634104.html


On 03/04/2011 04:15 PM, Sven Gothel [via jogamp] wrote:
>
> On Friday, March 04, 2011 11:57:53 gouessej [via jogamp] wrote:
>> Do you plan to benefit of the integer cache (see Integer.valueOf(int i))?
> Please enlight me.
> You mean the autoboxing is solved ?
> Alternative to out IntIntHashMap ?
>
java 5 has an internal mapping of at least +-128 Integer<->int entries
behind Integer.valueOf(int i).

answer: good idea we considered it already but we have in many cases
other values for 'i', e.g 64bit memory addresses. But yes this area is
certainly improvable.

It is also debatable if the state tracking is needed/should be
configurable in all situations, e.g i had an old custom jogl build
without state tracking at all for common things like VBOs as jogl was
still maintained by sun.

but:
even if it looks frightening on VisualVM there shouldn’t be any
noticeable performance impact. The objects are tiny and die young which
means they should not end up in the old genaration of the heap.

best regards,

michael

> ~Sven
>
>
> _______________________________________________
> If you reply to this email, your message will be added to the discussion below:
> http://forum.jogamp.org/Change-JogAmp-Module-s-Java-Language-Version-Constraints-tp2448646p2633351.html
> To start a new topic under jogamp, email [hidden email]
> To unsubscribe from jogamp, visit
http://michael-bien.com/