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

Issue 883521 link

Starred by 3 users

Issue metadata

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

Blocked on:
issue 839084



Sign in to add a comment

Regressions in rendering/system_health benchmarks due to disabling perfetto tracing backend

Project Member Reported by ushesh@chromium.org, Sep 12

Issue description

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

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


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

Android Nexus5 Perf

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

Revert "Reland "Enable Perfetto by default for all telemetry tests"" by oysteine@chromium.org
https://chromium.googlesource.com/chromium/src/+/00bea4ec5efd575a09604b89fbf6123b14690fb6
0.9382 → 2.291 (+1.352)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Blockedon: 839084
Components: Speed>Tracing
Summary: Regressions in rendering/system_health benchmarks due to disabling perfetto tracing backend (was: 137.4% regression in rendering.mobile at 586931:587003)
 Issue 883524  has been merged into this issue.
Issue 880455 has been merged into this issue.
Issue 880300 has been merged into this issue.
Mergedinto: 888558
Status: Duplicate (was: Assigned)

Sign in to add a comment