3 ms·
It's interesting how often the same stories play out for different interpreter implementations. Everyone tries: - a multi-pass JIT - interpretting the input d
by hinkley 4y ago
It's interesting how often the same stories play out for different interpreter implementations. Everyone tries:
- a multi-pass JIT
- interpretting the input directly to reduce time to first op
- making the fastest transpiler they can and skipping the interpreter
All of these are addressing different constraints and affect each other. For instance, a cheap transpiler is only slightly slower than an interpreter loop, and allows you to move the threshold for the JIT farther to the right. If you can avoid trying to optimize things that you will only be slightly successful at, you can invest more of your CPU budget in deeper optimization on the hottest paths. You are also running on-stack replacement less often, and in fewer scenarios, which may mean you make different tradeoffs there as well.