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

Issue 880328 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.7%-19012.9% regression in rendering.mobile at 586697:586852

Project Member Reported by maxlg@chromium.org, Sep 4

Issue description

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

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


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

android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: farahcharab@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12e1ba93640000

Scheduler: WebURLLoader should notify Blink with the initial priority. by farahcharab@google.com
https://chromium.googlesource.com/chromium/src/+/d2bade563869c5a429d129695ce754ca0f5e9507
16.66 → 232.2 (+215.5)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: Untriaged (was: Assigned)
Assigned, but no owner or component? Please find a component and/or owner

Sign in to add a comment