New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 887475 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

A zero-to-nonzero to 2.4% regression in rendering.desktop at 592380:592418

Project Member Reported by alexclarke@chromium.org, Sep 20

Issue description

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

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


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

linux-perf
mac-10_12_laptop_low_end-perf
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/13b23304e40000

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

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: oysteine@chromium.org
Mergedinto: 888558
Status: Duplicate (was: Assigned)
the metric reports 0 with perfetto - probably gets broken

Sign in to add a comment