New issue
Advanced search Search tips

Issue 917245 link

Starred by 2 users
Status: Assigned
Owner:
ccameron@chromium.org
Cc:
kouhei@chromium.org
ccameron@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

14.1% regression in rendering.desktop/thread_total_all_cpu_time_per_frame at 614130:614248

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

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

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

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


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

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 21

Cc: ccameron@chromium.org
Owner: ccameron@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12e6ae41140000

OOP-R: GrContext::flush and glFlush at every DoRasterCHROMIUM by ccameron@chromium.org
https://chromium.googlesource.com/chromium/src/+/b2615d69395f6922a2d5b727045cfd70b73445fe
thread_total_all_cpu_time_per_frame: 15.61 → 18.73 (+3.123)

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

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

Sign in to add a comment