New issue
Advanced search Search tips

Issue 911566 link

Starred by 2 users
Status: WontFix
Owner:
ccameron@chromium.org
Closed: Dec 5
Cc:
ccameron@chromium.org
toyoshim@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

13.5% regression in rendering.desktop/thread_total_all_cpu_time_per_frame at 612251:612447

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

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

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

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


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, Dec 4

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/12293572140000

OOP-R: GrContext::flush and glFlush at every DoEndRasterCHROMIUM by ccameron@chromium.org
https://chromium.googlesource.com/chromium/src/+/193f427a339c3e2016996c0018d55fa631b8dbf1
thread_total_all_cpu_time_per_frame: 16.25 → 18.34 (+2.094)

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

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

Comment 4 by ccameron@chromium.org, Dec 5 

This is an expected regression for the patch (adds a heavy workaround).

Comment 5 by ccameron@chromium.org, Dec 5

Status: WontFix (was: Assigned)
►

Sign in to add a comment