New issue
Advanced search Search tips

Issue 909628 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Dec 24
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.1%-34.6% regression in loading.mobile at 609905:610325

Project Member Reported by drott@chromium.org, Nov 28

Issue description

Splitting out mobile / Android results as they seem unrelated to the HarfBuzz Mac AAT change.

 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=909628

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=064103660dab74eae0641e79a4cceba71ea23840b27f5324bb1ad9319cb1e3e1


Bot(s) for this bug's original alert(s):

Android Nexus5X WebView Perf
Android Nexus6 WebView Perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

system_health.memory_mobile - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

speedometer - Benchmark documentation link:
  None

loading.mobile - Benchmark documentation link:
  https://bit.ly/loading-benchmarks
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/179e899fe40000
Components: -Blink Blink>Loader
Loading triage:

Kick another bisect for the test that showed the largest regression. But actually several tests were regressed, and the others were improved in that revision range. If we knew the root cause CL, it would help to consider if this regression could be acceptable or not.
😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14be9418140000

The swarming task expired. The bots are likely overloaded, dead, or misconfigured.
Cc: brianosman@google.com
Owner: brianosman@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/111176f4140000

Use a smaller tolerance when chopping conics to quads by brianosman@google.com
https://skia.googlesource.com/skia/+/e3deee131979b5e2c6ee07cad59a06c247a40d91
frame_times: 28.67 → 30.34 (+1.665)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
I believe that my CL would trigger a regression on that test page, but I also think it's justified. That page draws a large number of bouncing circles. Prior to my CL, none of them actually looked like circles, because we weren't subdividing the geometry enough. So they're slower now, but at least they look correct. (You can actually see the improvement by comparing http://themaninblue.com/experiment/AnimationBenchmark/canvas/ with stable vs. Canary). Also, see  crbug.com/888453 
Status: WontFix (was: Assigned)

Sign in to add a comment