Actually that might have been a little OTT But it would not be unreasonable to implement a VM that allocated objects on 32 byte boundaries…
Cas
Actually that might have been a little OTT But it would not be unreasonable to implement a VM that allocated objects on 32 byte boundaries…
Cas
I never said this was my bottleneck, it’s just that there are about 30000 values stored in hashmaps out of which about ~1000 need to be called per tick (1/60 second) or more, so I thought there might be a better way than boxing. It’s not critical at all, but why not optimize it
My bottleneck is - surprise, surprise - java2d
if your asking yourself why not make it efficient, the aswer should be yes.
if you truely wondering about optimising it, the answer should be no, not until your have profiled your app.
when did I ever say I didn’t profile it?? I even posted that I know what my bottleneck is in my very last post. >_<
ok I was beeing dense then. ;D
but even if you are profiling you pass my assertion, so no worries
Because, as the Great Abrash puts it…
“Things that don’t matter don’t matter.”
So why waste time and energy on them.