New issue
Advanced search Search tips

Issue 722185 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

96.7% improvement in system_health.memory_mobile at 470443:470492

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=722185

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


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

android-nexus5
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_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/browse_shopping/browse_shopping_avito
  Change       : 96.82% | 20828665.3333 -> 662954.666667

Revision             Result                   N
chromium@470442      20828665 +- 19890.1      6      good
chromium@470467      20822959 +- 21109.4      6      good
chromium@470480      20818841 +- 14019.1      6      good
chromium@470486      20821269 +- 12423.2      6      good
chromium@470489      20819468 +- 27956.4      6      good
chromium@470490      666157 +- 56088.8        6      bad       <--
chromium@470491      673229 +- 51259.3        6      bad
chromium@470492      662955 +- 63675.5        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/8979554126970793792

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


| 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_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/browse_shopping/browse_shopping_avito
  Change       : 96.76% | 20818840.6667 -> 673686.666667

Revision             Result                   N
chromium@470442      20818841 +- 14019.1      6      good
chromium@470467      20884855 +- 324634       6      good
chromium@470480      20819260 +- 9705.64      6      good
chromium@470486      20819468 +- 27956.4      6      good
chromium@470489      20818808 +- 29406.8      9      good
chromium@470490      2889969 +- 19027535      9      bad       <--
chromium@470491      679286 +- 14381.6        6      bad
chromium@470492      673687 +- 31930.8        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/8979554136885148864

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


| 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