New issue
Advanced search Search tips

Issue 918709 link

Starred by 2 users
Status: Fixed
Owner:
chrishtr@chromium.org
Closed: Today
Cc:
chiniforooshan@chromium.org
chrishtr@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

8.8% regression in rendering.desktop/thread_total_all_cpu_time_per_frame at 618982:618992

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=918709

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


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

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

Move visual overflow computation into the descendant-dependent tree walk. by chrishtr@chromium.org
https://chromium.googlesource.com/chromium/src/+/395a93a5ea18f0890a237d5e687a80b69f39a473
thread_total_all_cpu_time_per_frame: 17.06 → 18.13 (+1.073)

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

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

Sign in to add a comment