New issue
Advanced search Search tips

Issue 894106 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 11
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.1%-12.3% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 597084:597164

Project Member Reported by m...@chromium.org, Oct 10

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=894106

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


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

Android Nexus5 Perf
android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: -m...@chromium.org
Status: WontFix (was: Untriaged)
Cc: sadrul@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12d2882ae40000

Reland "synthetic gesture: Allow high-frequency dispatch." by sadrul@chromium.org
https://chromium.googlesource.com/chromium/src/+/a66784e0fd71f686f1d7152902137619608c6c80
thread_total_all_cpu_time_per_frame: 20.14 → 21.91 (+1.777)

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

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

Sign in to add a comment