3 ms·

Chrome does not specifically optimize for asm.js.

fulafel 11y ago
It does kinda, according to https://hacks.mozilla.org/2015/03/asm-speedups-everywhere/ https://hacks.mozilla.org/2015/03/asm-speedups-everywhere/
clouddrover 11y ago
Sure it does. Chrome has been specifically optimizing for asm.js for over two years (see [1]). Google's own Octane browser benchmark has included an asm.js benchmark for over two years (see [2][3][4]). Game developers have been commenting on Chrome's asm.js performance for over two years (see [5]). Chrome is just slower. Microsoft has done a good job with Edge's JavaScript engine. [1] http://blog.chromium.org/2013/05/chrome-28-beta-more-immersive-web.html http://blog.chromium.org/2013/05/chrome-28-beta-more-immersi... [2] http://blog.chromium.org/2013/11/announcing-octane-20.html http://blog.chromium.org/2013/11/announcing-octane-20.html [3] http://techcrunch.com/2013/11/06/google-updates-its-octane-javascript-benchmark-adds-asm-js-and-typescript-tests/ http://techcrunch.com/2013/11/06/google-updates-its-octane-j... [4] https://developers.google.com/octane/ https://developers.google.com/octane/ [5] https://www.scirra.com/blog/132/more-about-asmjs-powered-physics https://www.scirra.com/blog/132/more-about-asmjs-powered-phy...
- 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 ago
    Chrome 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 ago
      Huh. 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.

It does kinda, according to https://hacks.mozilla.org/2015/03/asm-speedups-everywhere/ https://hacks.mozilla.org/2015/03/asm-speedups-everywhere/

clouddrover 11y ago

Sure it does. Chrome has been specifically optimizing for asm.js for over two years (see [1]). Google's own Octane browser benchmark has included an asm.js benchmark for over two years (see [2][3][4]). Game developers have been commenting on Chrome's asm.js performance for over two years (see [5]). Chrome is just slower. Microsoft has done a good job with Edge's JavaScript engine. [1] http://blog.chromium.org/2013/05/chrome-28-beta-more-immersive-web.html http://blog.chromium.org/2013/05/chrome-28-beta-more-immersi... [2] http://blog.chromium.org/2013/11/announcing-octane-20.html http://blog.chromium.org/2013/11/announcing-octane-20.html [3] http://techcrunch.com/2013/11/06/google-updates-its-octane-javascript-benchmark-adds-asm-js-and-typescript-tests/ http://techcrunch.com/2013/11/06/google-updates-its-octane-j... [4] https://developers.google.com/octane/ https://developers.google.com/octane/ [5] https://www.scirra.com/blog/132/more-about-asmjs-powered-physics https://www.scirra.com/blog/132/more-about-asmjs-powered-phy...

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 ago
  Chrome 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 ago
    Huh. 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.