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

Issue 808656 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

12.2%-34.8% regression in loading.mobile at 533195:533258

Project Member Reported by npm@chromium.org, Feb 2 2018

Issue description

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

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


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

android-nexus5X
android-nexus6
android-one
Re-kicking the bisect. Looks like it reproduces, but didn't get to the culprit.
Cc: alexilin@chromium.org jwd@chromium.org xunji...@chromium.org
Owner: alexilin@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14af01fc440000

Enable SpeculativePreconnect Field Trial Testing by alexilin@chromium.org
https://chromium.googlesource.com/chromium/src/+/8442e044284223377ccd75e4f1b519c5656d4d8d

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

Comment 7 by 42576172...@developer.gserviceaccount.com, Mar 20 2018

Cc: lizeb@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12c585b9440000

predictors: Skip dns preresolution if a proxy is configured by alexilin@chromium.org
https://chromium.googlesource.com/chromium/src/+/b6e03254a007461585b9b484e620893630f127a8

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: Fixed (was: Assigned)
The metric has recovered after https://crrev.com/c/958913

Comment 9 by npm@chromium.org, Mar 21 2018

Status: Assigned (was: Fixed)
Thanks for the improvement from #7!

This bug has 11 graphs, and it's worth pointing out that there is a regression after this one in most graphs. However most timeToFirstMeaningfulPaint_avg graphs are not recovered at all. So I don't think this should be considered fully fixed. That is, I think we would see an improvement in these graphs if the field trial experiment was reverted.

Comment 10 by npm@chromium.org, Mar 21 2018

Actually it seems those graphs haven't caught up to that CL, so let's wait until they do to see if they recovered.
Status: WontFix (was: Assigned)
Sorry for being too eager to close this bug, you're right I had to wait until all graphs caught up to that CL. I think all of them have finally recovered from this regression.

Sign in to add a comment