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

Issue 886718 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

1.1% regression in memory.top_10_mobile at 590562:590599

Project Member Reported by alexclarke@chromium.org, Sep 19

Issue description

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

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


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

Android Nexus5 Perf

memory.top_10_mobile - Benchmark documentation link:
  None
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/15ab2f7b640000

Reland "Scheduler: WebURLLoader should notify Blink with the initial priority." by yhirano@chromium.org
https://chromium.googlesource.com/chromium/src/+/9fbd6bbc97324bc72d8fcb7bb7a846399517fdee
3.378e+07 → 3.428e+07 (+4.982e+05)

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

Benchmark documentation link:
  None
Cc: altimin@chromium.org
Status: WontFix (was: Assigned)
I relanded the CL as part of sheriff duty.

Sign in to add a comment