New issue
Advanced search Search tips

Issue 888549 link

Starred by 1 user
Status: Duplicate
Merged: issue 888558
Owner:
pasko@chromium.org
Closed: Sep 24
Cc:
kouhei@chromium.org
pasko@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

22.2% regression in rendering.desktop at 592380:592407

Project Member Reported by kouhei@google.com, Sep 24 
See the link to graphs below.
Project Member

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

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

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


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
Project Member

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

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/166b1324e40000

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

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

Comment 4 by pasko@chromium.org, Sep 24

Mergedinto: 888558
Status: Duplicate (was: Assigned)
Perfetto seems to cause less concurrency?
►

Sign in to add a comment