#enable-asm-webassembly not enabled by default
Reported by
jon...@zynga.com,
Jul 19 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: Our application performance testing indicates a significant increase in asm.js performance with #enable-asm-webassembly explicitly enabled (i.e. not left in default state). We've reproduced this on OSX and Windows 7. We can try to supply a test application if this is a real mystery. asm.js code (generated via emscripten) does include the 'use asm'. What is the expected behavior? Slower .asm .js performance without #enable-asm-webassembly. What went wrong? We had expected the default state of the #enable-asm-webassembly to be enabled. Did this work before? N/A Chrome version: 59.0.3071.115 Channel: stable OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 26.0 r0 Sorry this is all a big generic, we can try to provide a more detailed test if it's a real mystery. I believe the origin of this is probably our misunderstanding the nature of "asm.js to WASM conversion" being enabled by default.
,
Jul 25 2017
It is great to hear that you get a performance boost with the new pipeline! The new asm.js pipeline is not enabled on 59 Stable per default. We are currently aiming of activating it on 61 Stable though.
,
Jul 25 2017
,
Jul 25 2017
,
Jul 25 2017
That's great news. Just to confirm we did note a significant performance improvement on Chrome 58. With the #enable-asm-webassembly flag enabled however it improves further still. Frequently outperforming Firefox in our measures. Much obliged for this info.
,
Jul 27 2017
Indeed, glad to hear it. |
||||
►
Sign in to add a comment |
||||
Comment 1 by dtapu...@chromium.org
, Jul 19 2017