Earlier quoted context omitted.
The benchmarks are a little bit misleading for some types of code. They do not measure single run code well. In these cases pypy doesn't do as well as when the JIT has warmed up. The interpreter is slower than the CPython one. For code which doesn't JIT well, it will go slower with pypy. The firefox JS engine now has a fast interpreter, a quick JIT, and a more optimizing one. This means the baseline performance is be…
"The firefox JS engine now has a fast interpreter, a quick JIT, and a more optimizing one. This means the baseline performance is better in CPython" Huh?
- interpreted
- If run 'enough' times, the code is JIT compiled (fast compilation)
- If run 'enough' times again, it is JIT compiled with the most optimizing compiler (slow compilation)