New issue
Advanced search Search tips

Issue 876845 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Sep 10
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4%-75.2% regression in rendering.mobile at 584838:584919

Project Member Reported by majidvp@chromium.org, Aug 22

Issue description

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

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


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

Android Nexus5 Perf
Android Nexus6 WebView Perf
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/14f0fece640000

[scheduler] Enable prioritising compositing after input on waterfall by altimin@chromium.org
https://chromium.googlesource.com/chromium/src/+/e38ad59a34b356c0315e13da8829ba7ef78bfe6b
5.706 → 9.666 (+3.96)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
This is the side-effect of faster scrolling.

Sign in to add a comment