New issue
Advanced search Search tips

Issue 722192 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: May 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

69.8% improvement in system_health.memory_mobile at 470433:470513

Project Member Reported by yhirano@chromium.org, May 15 2017

Issue description

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgyvey3QgM


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

android-nexus6
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, May 15 2017

Mergedinto: 721238
Status: Duplicate (was: Assigned)

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : yhirano
  Commit : 91088a195969f5af61f404c9f02edc622cbe373a
  Date   : Wed May 10 05:49:31 2017
  Subject: Add Field Trial Testing Configuration for MojoLoading

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/browse_shopping/browse_shopping_avito
  Change       : 69.82% | 7604072.0 -> 2294840.0

Revision             Result                  N
chromium@470432      7604072 +- 0.0          5       good
chromium@470473      7604072 +- 0.0          6       good
chromium@470483      6719200 +- 4846644      6       good
chromium@470488      6424243 +- 6621776      9       good
chromium@470489      6719200 +- 4846644      6       good
chromium@470490      2294840 +- 0.0          6       bad       <--
chromium@470491      3053302 +- 6951416      14      bad
chromium@470493      2884755 +- 5005592      9       bad
chromium@470513      2294840 +- 0.0          6       bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.shopping.avito system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979553952437031280

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5491754620420096


| 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 Speed>Bisection.  Thank you!
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, May 15 2017


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : yhirano
  Commit : 91088a195969f5af61f404c9f02edc622cbe373a
  Date   : Wed May 10 05:49:31 2017
  Subject: Add Field Trial Testing Configuration for MojoLoading

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/browse_shopping/browse_shopping_avito
  Change       : 58.18% | 7604072.0 -> 3179712.0

Revision             Result                  N
chromium@470432      7604072 +- 0.0          9       good
chromium@470473      7604072 +- 0.0          9       good
chromium@470483      7604072 +- 0.0          9       good
chromium@470488      7604072 +- 0.0          9       good
chromium@470489      7604072 +- 0.0          9       good
chromium@470490      4190994 +- 9518619      14      bad       <--
chromium@470491      2884755 +- 5005592      9       bad
chromium@470493      3179712 +- 4846644      6       bad
chromium@470513      3179712 +- 4846644      6       bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.shopping.avito system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979553944433993360

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4982197989146624


| 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 Speed>Bisection.  Thank you!

Sign in to add a comment