New issue
Advanced search Search tips

Issue 911118 link

Starred by 1 user
Status: Fixed
Owner:
oysteine@chromium.org
Closed: Dec 12
Cc:
maxlg@chromium.org
oysteine@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocking:
issue 909795



Sign in to add a comment

3%-207.6% regression in rendering.desktop/thread_total_all_cpu_time_per_frame at 612736:612821

Project Member Reported by maxlg@chromium.org, Dec 3 
See the link to graphs below.
Project Member

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

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

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


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

linux-perf
mac-10_12_laptop_low_end-perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 3

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/12d142d2140000

Revert "Perfetto: Stop splitting _COMPLETE events" by oysteine@chromium.org
https://chromium.googlesource.com/chromium/src/+/6a796b426b1ff987c8e4fd63d838731bcfd50d54
thread_raster_cpu_time_per_frame: 0.9352 → 2.018 (+1.083)

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

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

Comment 4 by skobes@chromium.org, Dec 12

Blocking: 909795

Comment 5 by maxlg@chromium.org, Dec 12 

oysteine, do you have any update on this bug?

Comment 6 by oysteine@chromium.org, Dec 12

Status: Fixed (was: Assigned)
Yes, sorry, the CL relanded in crrev.com/614540 so all alerts should be recovered now.
►

Sign in to add a comment