3 ms·

True though oddly I compiled and ran them exactly the same way he described in the paper -- one time through, no warm-up time.

• Terr_ 12y ago
  I think the command-line option -XX:+PrintCompilation should show you if/when the JIT kicks in for a method.
• Alupis 12y ago
  The sample code is probably too predictable and the JVM was able to optimize it well. In any event... the "myth" that Java is slow is bogus :)