New issue
Advanced search Search tips

Issue 898905 link

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



Sign in to add a comment

13.9%-198.2% regression in rendering.desktop/thread_raster_cpu_time_per_frame at 600402:600739

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

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 25 

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

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


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

Win 7 Perf
linux-perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 25 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/11adb726e40000

Comment 4 by maxlg@chromium.org, Nov 20

Status: Fixed (was: Untriaged)
Based on the graph, the regression is caused by a revert.
►

Sign in to add a comment