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
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
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
Since the html pages are already cached, why not also cache the JIT
compiled javascript while leaving a page? Shouldn't use too much space
than the text content of the embedding page. Much less space than the
image files embedded in a page.
___
dev-p
4 matches
Mail list logo
