4 ms·
> But why not just cache the JITed code? What is the difference between AOT and sufficiently aggressive JIT caching? > Caching first-run still gives you the a
by DCKing 12y ago
> But why not just cache the JITed code?
What is the difference between AOT and sufficiently aggressive JIT caching?
> Caching first-run still gives you the ability to do more/new profiled-based optimization later.
Well you could have your runtime running with the overhead of an interpreter, a profiler, and an optimizer, and hope all will turn out well. Or you could just run the machine code without these complexities and know that it is probably close to optimal anyway.
- rockdoe 12y agoWhat is the difference between AOT and sufficiently aggressive JIT caching? AoT doesn't adapt to changing program profiles.
- deong 12y agoBut it also doesn't spend any CPU time, memory pressure, cache lines, etc., on trying to adapt to changing profiles.
- DCKing 12y agoWell, I think the answer to you question then would have to be that not enough advantage could be gained from changing program profiles to compensate the disadvantages of JIT.
- pjmlp 12y agoYeah, but AOT + PGO does.