Without digging into the actual reasons, it's likely that growing a
larger arraylist is slower than growing a smaller one, and since you
never clear it, the later calls will therefore be slower. I would very
much like a benchmark of method call time to be allocation- and
garbage-free, otherwise I really don't know what's being tested.
S.
On 04/07/2017 06:28 PM, J Crawford wrote:
Hello,
I think here might be the best place to find someone who may know what’s
going on with the JVM in that
test:
http://stackoverflow.com/questions/43281743/what-happens-inside-the-jvm-so-that-a-method-invocation-in-java-becomes-slower-w
Basically I warmup a method and then when I call it on another location
(few lines below) it is much slower. Trying to understand and mitigate
this effect so my method invocation is consistently fast.
Thanks!
-JC
--
You received this message because you are subscribed to the Google
Groups "mechanical-sympathy" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to mechanical-sympathy+unsubscr...@googlegroups.com
<mailto:mechanical-sympathy+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"mechanical-sympathy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mechanical-sympathy+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
