Version: 53.0.2747.0
OS: Android4
Run at: https://trac.webkit.org/export/HEAD/trunk/PerformanceTests/Animometer/developer.html
I'm testing with --force-gpu-rasterization.
This test on N6 will score either 1, or ~130. When tracing, both cases are pegged on the Main thread.
I suspect this is the difference between the main thread running on different cores (big.LITTLE). Unfortunately I couldn't get adb_profile_chrome with systracing to run and confirm.
On Galaxy S7 Edge (US) I noticed that we also get binary behavior but during a single run, the trace shows patterns of running fast and slow.
May be worth looking at thread priorities, and how to get Main thread to run on Big cores when we are Main thread driven.
Comment 1 by esprehn@chromium.org
, Jun 2 2016