Re:ARMv7 vs. x86-64: Pathfinding benchmark of C++, D, Go, Ni...
by th0br0 on Saturday December 20, 2014 @06:57AM
(#8776428)
It seems to me though, that the Java numbers aren't representative. As far as I know, JVM benchmarks should allow HotSpot etc to optimise the functions by calling them ~1k times before the actual benchmark happens. That doesn't seem to be the case in the code.
[ Parent
| on HN ]
Re:ARMv7 vs. x86-64: Pathfinding benchmark of C++, D, Go, Ni...
by logicchains on Saturday December 20, 2014 @07:07AM
(#8776445)
The same function is being called over and over millions of times, so hopefully that should give HotSpot a chance to kick in. I didn't want to add artificial warm up as I don't think that's representative of real code.
Re:ARMv7 vs. x86-64: Pathfinding benchmark of C++, D, Go, Ni...
by igouy on Sunday December 21, 2014 @02:20AM
(#8779200)
Check times with JMH
http://openjdk.java.net/projects/code-tools/jmh/
Also -XX:-PrintCompilation -XX:-PrintGC
https://wikis.oracle.com/display/HotSpotInternals/MicroBench...