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

Issue 883382 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

27.9% regression in loading.mobile at 590215:590249

Project Member Reported by ushesh@chromium.org, Sep 12

Issue description

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

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


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

Android Nexus5 Perf

loading.mobile - Benchmark documentation link:
  https://bit.ly/loading-benchmarks
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/177296d7640000

Revert "Scheduler: WebURLLoader should notify Blink with the initial priority." by yhirano@chromium.org
https://chromium.googlesource.com/chromium/src/+/3ce3af5c962d5692f2979846628f3c4b8ceb3e30
684.1 → 827.3 (+143.2)

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

Benchmark documentation link:
  https://bit.ly/loading-benchmarks
Cc: altimin@chromium.org
Status: WontFix (was: Assigned)
This is a revert CL.

Sign in to add a comment