New issue
Advanced search Search tips

Issue 914857 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

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

Project Member Reported by skobes@google.com, Dec 13

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=914857

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


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
Blocking: 909795
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/13abc43a140000

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: 59.26 → 191.4 (+132.2)

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

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

Comment 5 by skobes@chromium.org, Jan 16 (6 days ago)

Blocking: -909795

Sign in to add a comment