A big part of the score is compilation time, which improves a lot with Liftoff, our baseline compiler for WebAssembly in V8. We've been in contact with the benchmark authors and have identified other bottlenecks in our engine (e.g. instantiation time), which we are now working on optimizing. Look forward to some increasing scores soon :)
Liftoff is still substantially slower at initial compilation than Firefox. Are there any plans to close the gap? A Unity exported game takes over 40 seconds for a new model low end Chromebook to compile. The upcoming 3 fold decrease will be nice, but FF could do it in 2 seconds on the same hardware.
https://lukewagner.github.io/test-tanks-compile-time/
FF 61: 78.4 MB/s
Chrome Canary: 9.7 MB/s
Chrome 67: 3.3 MB/s
We still have a bottleneck at instantation time where we compile many JS<->WASM wrappers. We are working on parallelizing this compilation as well, so we'll get another bump out of that.
Pretty soon we will be running Chrome on Firefox.
IIRC they've also always had the fastest Typed Arrays. I wonder if there is a connection there - it wouldn't surprise me if memory access is the biggest bottleneck for WASM in other browsers.
Have you tried enabling the experimental new WebAssembly baseline compiler in Chrome Canary?
As a matter of fact, I just did! Still getting crushed at 4546
Check with --js-flags="--no-untrusted-code-mitigations", it should be about 10-13% faster.
https://github.com/v8/v8/wiki/Untrusted-code-mitigations
This does not sound safe.
Aw, Snapped! on me
On my phone (OP6) FireFox beats Chrome by two whole seconds
Samsung Galaxy S9+ (w/ Exynos):
Firefox: 6900
Firefox Nightly: 7874
Google Chrome: 10602
Moto G4 phone Chrome: 37735
Windows 10 Laptop: