3 ms·
improvements for typical benchmark code nothing for common user code why? because benchmarking JIT code is cheating, nobody runs THE SAME code path 1_000_000
by Shadonototra 5y ago
improvements for typical benchmark code
nothing for common user code
why?
because benchmarking JIT code is cheating, nobody runs THE SAME code path 1_000_000 times in a row to warmup the JIT
you run something here, then there, then over there, then sometimes there, this is not JIT proof and you constantly get the JIT to do work
that's part of the reason Go became popular, on top of the single binary and the cloud native libraries story