New issue
Advanced search Search tips

Issue 877584 link

Starred by 1 user
Status: WontFix
Owner:
altimin@chromium.org
Closed: Sep 10
Cc:
m...@chromium.org
altimin@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.7%-102% regression in rendering.mobile at 584838:584919

Project Member Reported by m...@chromium.org, Aug 24 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 24 

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

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


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

Android Nexus5 Perf
Android Nexus6 WebView Perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 26

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/16a98cf9640000

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

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

Comment 4 by altimin@chromium.org, Sep 10

Status: WontFix (was: Assigned)
This is the side-effect of us rendering earlier (which is a desired effect).
►

Sign in to add a comment