New issue
Advanced search Search tips

Issue 902452 link

Starred by 1 user
Status: Assigned
Owner:
wjmaclean@chromium.org
Cc:
wjmaclean@chromium.org
lanwei@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

41.7%-486% regression in rendering.desktop/thread_raster_cpu_time_per_frame at 605437:605503

Project Member Reported by lanwei@chromium.org, Nov 6 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 6 

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

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


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

mac-10_12_laptop_low_end-perf
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, Nov 7

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

Plumb page scale factor to oopifs via SynchronizeVisualProperties. by wjmaclean@chromium.org
https://chromium.googlesource.com/chromium/src/+/2a90bffaa3407289c413cb385e631e70547c586e
thread_raster_cpu_time_per_frame: 0.5516 → 3.285 (+2.733)

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

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

Sign in to add a comment