New issue
Advanced search Search tips

Issue 655131 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jan 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.6%-204.9% regression in memory.top_10_mobile_stress at 422374:424542

Project Member Reported by tdres...@chromium.org, Oct 12 2016

Issue description

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgjbf-tQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgjb_28gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9d_P_woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzZeGrwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzfHfugsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgjZu2hQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgze7ArAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzdbVuQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgrZDxogoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzbr-pQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzdy7vQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzaD86QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgjcngugsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzdeypAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzbiu6AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzdfZrAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgjbuW4QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzc2IuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzZ6GvwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgjf-a_ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzdO2pwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzbyeuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgrdCergoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzfLK9QkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgzbWeqwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgjfHlqQsM


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

android-nexus5
android-nexus5X
android-nexus6
android-nexus7v2
android-nexus9
android-one
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 12 2016


===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@424458  3803705  1863551  18  good
chromium@424460  4529038  1643951  18  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 655131

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile_stress
Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:ashmem:proportional_resident_size_avg/foreground/https_www_google_co_uk_hl_en_q_science
Relative Change: 41.42%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1712
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999004404215277280


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5309544765325312

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Oct 26 2016


===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@424000  4885504  1216992  18  good
chromium@424486  5204764  147535   18  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 655131

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=https.www.google.co.uk.hl.en.q.science memory.top_10_mobile_stress
Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:ashmem:proportional_resident_size_avg/foreground/https_www_google_co_uk_hl_en_q_science
Relative Change: 3.07%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1763
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997728045172506400


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5790549930409984

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!
Status: Archived (was: Untriaged)
Archiving as bisection is difficult and there's been no movement.

Sign in to add a comment