New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 886709 link

Starred by 1 user
Status: Assigned
Owner:
altimin@chromium.org
Cc:
yhirano@chromium.org
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.3%-779.1% regression in rendering.mobile at 590559:590599

Project Member Reported by alexclarke@chromium.org, Sep 19 
See the link to graphs below.
Project Member

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

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

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


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
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 22

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

Reland "Scheduler: WebURLLoader should notify Blink with the initial priority." by yhirano@chromium.org
https://chromium.googlesource.com/chromium/src/+/9fbd6bbc97324bc72d8fcb7bb7a846399517fdee
8.495 → 48.06 (+39.57)

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

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

Comment 4 by yhirano@chromium.org, Sep 25

Owner: altimin@chromium.org
I relanded the CL as part of sheriff duty.
►

Sign in to add a comment