3 ms·
Let me clarify: Chrome does not to my knowledge contain any special optimizations that are only active in asm.js mode. Firefox does, to the extent of having an
by FeepingCreature 11y ago
Let me clarify: Chrome does not to my knowledge contain any special optimizations that are only active in asm.js mode. Firefox does, to the extent of having an entire separate codepath for asm.js AOT compilation.
- clouddrover 11y agoChrome contains special optimizations that are only active in asm.js mode: http://blog.chromium.org/2015/07/revving-up-javascript-performance-with.html http://blog.chromium.org/2015/07/revving-up-javascript-perfo... I don't know what you're arguing here. It doesn't matter what approach is taken to optimizing performance, all that matters is the performance achieved. Chrome is simply slower. Microsoft is to open source Edge's JavaScript engine (https://blogs.windows.com/msedgedev/2015/12/05/open-source-chakra-core/ https://blogs.windows.com/msedgedev/2015/12/05/open-source-c...), so perhaps the Chrome developers can study that for ideas on speeding up Chrome.
- FeepingCreature 11y agoHuh. Fair enough, cool I guess. It was my impression that for a long time, Chrome's stance was basically "We aren't gonna bother optimizing specifically for asm.js; instead, we're just gonna make JS faster in general." Which would seem to explain why > Chrome's head start hasn't helped it beat Edge in this benchmark.