New issue
Advanced search Search tips

Issue 897106 link

Starred by 1 user
Status: Assigned
Owner:
altimin@chromium.org
Cc:
altimin@chromium.org
hjd@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

40.9% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 599623:599644

Project Member Reported by hjd@google.com, Oct 19 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 19 

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

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


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

Android Nexus6 WebView Perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 19

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

[scheduler] Disable scheduling input heuristics on waterfall. by altimin@chromium.org
https://chromium.googlesource.com/chromium/src/+/bd99ba315dcde886153185de166fafd3b0b959a8
thread_total_all_cpu_time_per_frame: 20.84 → 27.87 (+7.023)

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

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

Sign in to add a comment