3 ms·
I get 157K/sec in the terminal and 309K/sec in Chrome. As the article says, Chrome's performance shows wide variation, even after JIT warmup. It's ranging from
by panarky 13y ago
I get 157K/sec in the terminal and 309K/sec in Chrome.
As the article says, Chrome's performance shows wide variation, even after JIT warmup. It's ranging from 50K/sec to 320K/sec. Bizarre.
- azakai 13y agoJITs are great but can be unpredictable, that's probably the cause. As mentioned in the article, JITs vs AOT have upsides and downsides.
- steveklabnik 13y agoDoesn't Chrome specifically _not_ optimize asm.js, as well? Wonder if that has anything to do with it.
- zurn 13y agoIt doesn't special case the asm.js JS subset same way as Firefox does, but V8 guys are paying attention to optimizing asm.js-style code.