New issue
Advanced search Search tips

Issue 828410 link

Starred by 1 user
Status: WontFix
Owner:
dproy@chromium.org
Closed: Nov 26
Cc:
benjhayden@chromium.org
dproy@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

64.9% regression in system_health.common_mobile at 545911:545939

Project Member Reported by pmeenan@chromium.org, Apr 3 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Apr 3 2018 

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

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


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

android-nexus5
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 3 2018 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/16973fdf440000

Comment 5 by sullivan@google.com, May 3 2018 

Bisecting on a wider range.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, May 3 2018

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

Get navigation info without using FrameLoader snapshots by dproy@chromium.org
https://chromium.googlesource.com/catapult/+/5d35a2c7122c1ac4a9a37e7743a19f628f25a38b

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

Comment 7 by sullivan@chromium.org, Jul 20

Components: Speed>Metrics>SystemHealthRegressions

Comment 8 by pmeenan@chromium.org, Jul 30

Cc: -pmeenan@chromium.org

Comment 9 by benhenry@chromium.org, Aug 2

Components: -Speed>Metrics>SystemHealthRegressions

Comment 10 by benhenry@chromium.org, Aug 2

Components: Speed>Metrics>SystemHealthRegressions

Comment 11 by npm@chromium.org, Nov 26 

Ping! This bug has been flagged as stale by Chrome Speed Metrics bug triage, and it has an owner. Any update on this issue?

Comment 12 by dproy@chromium.org, Nov 26

Status: WontFix (was: Assigned)
The value changed because we're now seeing an extra URL in the histogram: before (http://screen/7X7ynLMeBv8) vs after (http://screen/7GXqyQCFp3L). 

Some metrics could not be computed before due to lack of FrameLoader snapshot, but the new method of computing URLs doesn't require the presence of a FrameLoader snapshot, so we can calculate metric in more instances. This is WAI.
►

Sign in to add a comment