Hi all,
In the latest Chrome browser beta version WebGL performance is reduced by 90%. This is observed in version 60.0.3112.40. Earlier beta 60 versions did not exhibit this. This has been observed in the Angry boys demo and KoGaMa.com.
This has been reproduced on Win 7, Win 8.1 and Win 10
Indeed. We filed a bug with the chromium project under https://bugs.chromium.org/p/chromium/issues/detail?id=735955
Hi,
Could you either share the benchmarking script or a web assembly build? I would love to do some web assembly benchmarking!
This http://beta.unity3d.com/jonas/benchmark2015.zip should be good for you to build and try out.
Hi,
I benched marked both wasm and asm in various versions of Chrome. In Chrome 61 asm and wasm performance is the same. I believe that Chrome converts the asm on the fly! Look for the comment by Timothy Gu in the following:
https://v8project.blogspot.dk/2017/05/launching-ignition-and-turbofan.html?m=1
If true, this is obviously great news. But do you guys think there is any real drawbacks here?
I’m currently on Unity 5.3.8 and updating my project to 5.6.x is a real hassle in order to support wasm. Now I wonder if I even need to.
They do that indeed and the drawback could be a Chrome bug with WASM that wouldn’t happen with asm.js but we haven’t encountered any yet.
If you export for WASM with Unity you can save some startup time since Chromes doesn’t have to do the conversion itself and it can be used in other browsers too that don’t do the internal conversion but support asm.js and wasm.
Do you know which browsers does this?
Chrome is the only one that does this.
Hi,
Chrome 61 is out. I am unsure if asm.js is auto converted in the release even though it was in the beta and canary. Do you guys know if it is?