New issue
Advanced search Search tips

Issue 890866 link

Starred by 2 users
Status: Assigned
Owner: ----
Cc:
tdres...@chromium.org
antrim@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.3%-20.7% regression in rendering.desktop/thread_raster_cpu_time_per_frame at 595074:595103

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

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

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

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


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, Oct 1

Cc: antrim@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14ff91dce40000

Make robot account request a one-time call by antrim@google.com
https://chromium.googlesource.com/chromium/src/+/b3eeabcc09765cccfae50e98003ac2b7a51a2b67
0.07102 → No values

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

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

Sign in to add a comment