Issue metadata
Sign in to add a comment
|
WebAssembly: Android Performance is too slow
Reported by
gauravde...@gmail.com,
Aug 16 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36 Steps to reproduce the problem: 1. Open any medium sized WebAssembly webpage (in WebWorker) on android phone like Samsung Galaxy S4 or Nexus/Pixel 2. Note the time taken to AOT (time before first line of main). Compare the timings against Firefox on same device or native application. 3. Throughput after AOT is not captured as part of this bug What is the expected behavior? Startup time should be faster based on hardware of device (as the startup time is fast on desktop windows machine) What went wrong? AOT timings are high on android mobile phone for Webassembly in WebWorker Did this work before? N/A Chrome version: 60.0.3112.90 Channel: n/a OS Version: 10.0 Flash Version:
,
Aug 22 2017
The issue seems to be related to OS-Android. Hence, adding the appropriate OS. Thanks...!!
,
Aug 23 2017
This is a known issue and not unique to Android.
,
Nov 3 2017
,
Nov 4 2017
Indexeddb (storing wasm module there) would help a big way (with AOT compilation). FF is able to provide faster startup with same RAM (and L2 cache) - perhaps something more than could be done specifically for android (based on mobile device constraints) - eg lower memory footprints, optimal usage of cores, better throttling parameters (if applicable)
,
Nov 10 2017
IDB support is on it's way. We also have more general plans to improve caching. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by bokan@chromium.org
, Aug 16 2017