New issue
Advanced search Search tips

Issue 888521 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 888558
Owner: ----
Closed: Sep 24
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

35.2% regression in rendering.desktop at 592380:592407

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=888521

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


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

mac-10_13_laptop_high_end-perf

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

Revert "Reland "Enable Perfetto by default for all telemetry tests"" by pasko@chromium.org
https://chromium.googlesource.com/chromium/src/+/f36de8b1bdc40bf31455b052ef63338072b093da
32.49 → 45.87 (+13.39)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Mergedinto: 888558
Owner: ----
Status: Duplicate (was: Assigned)

Sign in to add a comment