New issue
Advanced search Search tips

Issue 888861 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Sep 25
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.7%-2273.4% regression in rendering.mobile/tasks_per_frame_total_all at 593324:593393

Project Member Reported by kouhei@google.com, Sep 25

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=888861

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


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

Android Nexus5X WebView Perf
Android Nexus6 WebView Perf
android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: jbudorick@chromium.org
Owner: jbudorick@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/126e7b70e40000

Use vpython and remove vendored pymock. by jbudorick@chromium.org
https://chromium.googlesource.com/catapult/+/23c67a511280f6dbc2a2bea849dd7eed5104809e
0.01869 → No values

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Status: Fixed (was: Assigned)
Culprit was reverted.

Sign in to add a comment