New issue
Advanced search Search tips

Issue 900886 link

Starred by 1 user
Status: Duplicate
Merged: issue 888558
Owner:
oysteine@chromium.org
Closed: Nov 2
Cc:
oysteine@chromium.org
hjd@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

10.3% regression in rendering.desktop/thread_total_all_cpu_time_per_frame at 603930:603974

Project Member Reported by hjd@google.com, Nov 1 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 1 

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

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


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

linux-perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 1

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/15991121e40000

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@chromium.org
https://chromium.googlesource.com/chromium/src/+/3bb24369bef996b43b2d2711f0033ba472f779ea
thread_total_all_cpu_time_per_frame: 2.111 → 2.29 (+0.1791)

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

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

Comment 4 by oysteine@chromium.org, Nov 2

Mergedinto: 888558
Status: Duplicate (was: Assigned)
►

Sign in to add a comment