New issue
Advanced search Search tips

Issue 888572 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.6%-648.5% regression in rasterize_and_record_micro.top_25 at 593280:593366

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

Issue description

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

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


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

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

rasterize_and_record_micro.top_25 - Benchmark documentation link:
  None

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/1394138f640000

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

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

Benchmark documentation link:
  None
Status: Fixed (was: Assigned)
culprit reverted

Sign in to add a comment