New issue
Advanced search Search tips

Issue 918706 link

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



Sign in to add a comment

16.7% regression in rendering.desktop/thread_total_all_cpu_time_per_frame at 618631:618679

Project Member Reported by chiniforooshan@chromium.org, Jan 2 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 2 

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

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


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, Jan 3

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

Short term fix for SkClipStack unique key issue by robertphillips@google.com
https://skia.googlesource.com/skia/+/427966a1c4dfe14df1b5a36cb65b140633c3ea58
thread_total_all_cpu_time_per_frame: 89.93 → 101.7 (+11.81)

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

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

Sign in to add a comment