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

Issue 804320 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 806036



Sign in to add a comment

7.4%-9.8% regression in loading.mobile at 530042:530104

Project Member Reported by pmeenan@chromium.org, Jan 22 2018

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 22 2018

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

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


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

android-nexus6
android-nexus7v2
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Jan 22 2018

๐Ÿ“ Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12bba898840000
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 22 2018

๐Ÿ“ Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/12bba898840000
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Jan 23 2018

๐Ÿ“ Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14ded4f8840000
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Jan 23 2018

๐Ÿ“ Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14ded4f8840000
Cc: dtu@chromium.org simonhatch@chromium.org
+dtu, simonhatch: Any idea why these bisects didn't produce values?

Trying on N7.
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Jan 29 2018

๐Ÿ“ Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/149ac9da840000
Blockedon: 806036
Bots are down: crbug.com/806036
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Jan 30 2018

Cc: ricea@chromium.org yhirano@chromium.org
Owner: ricea@chromium.org
Status: Assigned (was: Untriaged)
๐Ÿ“ Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/149ac9da840000

Always use backpressure for fetch
By ricea@chromium.org ยท Thu Jan 18 06:11:48 2018
chromium @ e0eac774de0cea10625eea2cb68f70310b05f764

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

Comment 10 by ricea@chromium.org, Jan 30 2018

I think I will have to revert it, at least for M65.

Could you tell me where to find the "To Run This Test" link?

Comment 11 by ricea@chromium.org, Jan 30 2018

Components: Blink>Network>FetchAPI

Comment 12 by ricea@chromium.org, Mar 22 2018

Status: Fixed (was: Assigned)
The change has been reverted. To avoid confusion, I am closing this issue. I have created a issue 824650 to track the work to re-land without a performance regression.

Sign in to add a comment