New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 865363 link

Starred by 2 users
Status: Assigned
Owner:
herhut@chromium.org
Cc:
█ n...@zynga.com
█ snavel...@zynga.com
titzer@chromium.org
adamk@chromium.org
dschuff@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Lower performance from Chrome 65 to 69 for Zynga application

Project Member Reported by titzer@chromium.org, Jul 19 
(forked from https://bugs.chromium.org/p/chromium/issues/detail?id=845851)

Steps to reproduce the problem:
1. Open the webassembly sample application https://skypebot.farm2.zynga.com/ (It akes around 20 seconds to load, its a sample cubes application)
2. Check all the boxes below (Make sure 15*15*15 cubes is selected)
3. Note the FPS at the top
4. There is wide difference between observed FPS in Chrome 66 vs Chrome 65

The fix from (https://bugs.chromium.org/p/chromium/issues/detail?id=849098) improved the FPS but not brought it back to Chrome 65 levels.

Data below (supplied by Zynga) 
(Choose 25 * 25 * 25 cubes (and all boxes checked)
Chrome 65 ---> 9 FPS
Chrome 67.0.3396.99 ---> 4.2 FPS
Chrome Canary 69.0.3482.0 ----> 7.4 FPS

Testing with our game we have
For Windows 10 
Chrome 65  - 34 FPS
Chrome Live - 23 FPS
Chrome Canary - 27 FPS

Comment 1 by sarves...@gmail.com, Jul 19 

Some more FPS numbers based on our recent profiling

Chrome 65 (pre Spectre) - 16 FPS
Current Chrome Live - 8 FPS 
Current Chome Canary 69 (with binary search fix - yet to be released) - 10 FPS

Can you highlight more about the code change done which caused the FPS to drop down? Maybe based on that if we avoid programming constructs in that area (like for example if the change was related to jmp tables, then maybe we avoid code which uses those, though I do not know whether that is realistic or whether it would be at all possible to do so...unless we understand more about the nature of the change itself)

Comment 2 by herhut@chromium.org, Jul 19 

Could you try measure passing --js-flags="--no-untrusted-code-mitigations" to chrome canary 69 and see what difference that makes?

Comment 3 by sarves...@gmail.com, Jul 20 

For the app https://skypebot.farm2.zynga.com/ 

25*25*25 selected and all boxes checked

Chrome 65

11 FPS

Chrome Live 67.0.3396.99

4.2 FPS

Chrome Canary 69.0.3496.0 (without the flag)

5.7 FPS 25*25*25 (All boxes checked)

Chrome Canary 69.0.3496.0 - (with the flag --no-untrusted-code-mitigations)

6.6 FPS 25*25*25 (All boxes checked)

Comment 4 by titzer@chromium.org, Jan 16 (6 days ago) 

Untrusted code mitigations should be turned off by default now. Are you still experiencing slowness? With Chrome 71 on Linux I am seeing ~11fps with 25x25x25 and the boxes checked.
►

Sign in to add a comment