New issue
Advanced search Search tips

Issue 876088 link

Starred by 1 user
Status: Fixed
Owner:
alexilin@chromium.org
Closed: Sep 12
Cc:
alexilin@chromium.org
hjd@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

18.7% regression in loading.mobile at 584120:584182

Project Member Reported by hjd@google.com, Aug 20 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 20 

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

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


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

Android Nexus5 Perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 21 

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/1249fc81640000

The swarming task expired. The bots are likely overloaded, dead, or misconfigured.
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Aug 30

Cc: alexilin@chromium.org
Owner: alexilin@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/117cd8cd640000

predictors: Use NetworkContext's APIs to preconnect sockets and resolve hosts. by alexilin@chromium.org
https://chromium.googlesource.com/chromium/src/+/5b417db655388d726c0724f5a12425a5ddd68904
2.704e+04 → 3.281e+04 (+5762)

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

Comment 6 by alexilin@chromium.org, Sep 12 

I believe the graphs have recovered from this regression after https://crrev.com/c/1202222 (Point ID: 589877).

Comment 7 by alexilin@chromium.org, Sep 12

Status: Fixed (was: Assigned)
►

Sign in to add a comment