New issue
Advanced search Search tips

Issue 880427 link

Starred by 1 user
Status: WontFix
Owner:
oysteine@chromium.org
Closed: Sep 4
Cc:
oysteine@chromium.org
tguilbert@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

12.5%-18.1% regression in media.desktop at 586980:587001

Project Member Reported by tguilbert@chromium.org, Sep 4 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 4 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=880427

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


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

mac-10_13_laptop_high_end-perf

media.desktop - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 4

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/17d27e7d640000

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

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

Comment 4 by tguilbert@chromium.org, Sep 4

Status: WontFix (was: Assigned)
It seems like there is no regression. The change is due to using a different type of tracing.
►

Sign in to add a comment