Re: The browser should cache compiled javascript code while caching html pages

On 10/17/2014 06:43 PM, Luke Wagner wrote: I have a short summary of why caching JIT code is not necessarily a clear win for most JS in a blog post: http://blog.mozilla.org/luke/2014/01/14/asm-js-aot-compilation-and-startup-performance/#caching We do machine code for asm.js, though (as also

Re: The browser should cache compiled javascript code while caching html pages

I have a short summary of why caching JIT code is not necessarily a clear win for most JS in a blog post: http://blog.mozilla.org/luke/2014/01/14/asm-js-aot-compilation-and-startup-performance/#caching We do machine code for asm.js, though (as also described in the post). More interesting than

Re: The browser should cache compiled javascript code while caching html pages

This question returns every so often. If I recall correctly: - the JIT-compiled code is much, much, much larger than the JS source code, and just reading it from the cache may actually slow down execution of the page; - in many pages, JIT-compiled code actually depends on the interactions between