Why chrome/chromium webassembly launching performance is the lowest?
Reported by
shader.y...@gmail.com,
Mar 30 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: 1. Access test link https://www.mujigame.com/muji/samurai2/index.html on PC or macOS 2. Watch the logs for webassembly launching time 3. Accumulate the 5 phases time to do comparison What is the expected behavior? I think chrome/chromium performance would be not lower than others. What went wrong? The actual result is chrome/chromium performance is the lowest. Did this work before? N/A Chrome version: 65.0.3325.181 Channel: stable OS Version: OS X 10.13.3 Flash Version:
,
Apr 1 2018
,
Apr 3 2018
Able to reproduce the issue on Mac 10.13.3, Win-10 and Ubuntu 14.04 using chrome reported version #65.0.3325.181 and latest canary #67.0.3387.0. This is a non-regression issue as it is observed from M60 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Apr 3 2018
This is generally due to Chrome/V8's single-tier system for WebAssembly. We're working on a faster startup tier that will pull us more in line with Mozilla, which we hope to get sometime in Q2.
,
Apr 4 2018
Helpful information, looking forward the high performance version, thanks all!
,
Apr 10 2018
,
Jun 27 2018
Please provide any news about new faster startup tier. Q2 is almost over. This is a critical issue for many developers.
,
Jun 28 2018
Hi, Liftoff is on track to launch in Chrome 69.
,
Jul 31
Hello, it seems that Liftoff was disabled with Chrome 70. There was a big performance improvement with Chrome 69, but it gone with Chrome 70.
,
Aug 9
Marking as fixed. c9: You might have fallen victim to our infrastructure flipping the feature on/off for A/B testing. It should be turned on by default in 70 now. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by rtoy@chromium.org
, Mar 30 2018