New issue
Advanced search Search tips

Issue 833275 link

Starred by 1 user
Status: WontFix
Owner:
u...@chromium.org
Closed: Sep 3
Cc:
perezju@chromium.org
charliea@chromium.org
toyoshim@chromium.org
u...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.1%-18.5% regression in system_health.memory_mobile at 550002:550107

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

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

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

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


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

android-nexus6
android-one
Project Member

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

Cc: perezju@chromium.org u...@chromium.org charliea@chromium.org
Owner: u...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1593e3fac40000

Reduce noise of memory metric. by ulan@chromium.org
https://chromium.googlesource.com/catapult/+/64d08119f342961a5dd64049a03a50d36585899c

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

Comment 4 by benhenry@chromium.org, Aug 2

Components: Speed>Metrics>SystemHealthRegressions

Comment 5 by benhenry@chromium.org, Aug 2

Components: -Speed>Metrics>SystemHealthRegressions

Comment 6 by u...@chromium.org, Sep 3

Status: WontFix (was: Assigned)
This was a metric change and does not affect production Chrome.

The pinpoint job shows that the benchmark was bi-modal before and now stabilized at the higher value.
►

Sign in to add a comment