Um, as I understand it, you load the two operands from memory, which is as fast as the CPU, then perform the operation. That's 3 ticks. What's java doing, compiling itself?
I gave it 100 for the possibly bs notion that memory access is slow. Or maybe java just compiles itself every time we change a variable and then runs for no reason. (no reason because the variables would all be compiled in statically if they recompile every time)
And what about C? It doesn't have a JiT.
If you're getting 30mhz, they're probably getting 40. mhz. In C?
There's a full spectrum of possibilities, but I don't think activating naiive bench optimizations is going to cure our miserable Minecraft FPS. Or the experience. But we don't like to talk about that.