Issue metadata
Sign in to add a comment
|
1%-11.1% regression in memory.top_10_mobile at 463387:463752 |
||||||||||||||||||||
Issue descriptionugh
,
Apr 17 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982023360039891648
,
Apr 18 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_one_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background_search/background_search_google Revision Result N chromium@463595 32307973 +- 6869943 21 good chromium@463672 31556843 +- 8804731 21 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=background.search.google system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982023360039891648 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5828354780954624 | 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!
,
Apr 18 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982012718269304240
,
Apr 18 2017
=== BISECT JOB RESULTS === Perf regression found but unable to narrow commit range Build failures prevented the bisect from narrowing the range further. Bisect Details Configuration: android_one_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background_search/background_search_google Change : 7.55% | 32494681.9048 -> 30040982.8571 Suspected Commit Range 9 commits in range https://chromium.googlesource.com/chromium/src/+log/8d6ca52da9023346a99527fc6803ef26538f4b03..d38bc1e5ea6641c9085757251e9246c39363f7ec Revision Result N chromium@463595 32494682 +- 7020820 21 good chromium@463604 32375776 +- 5167547 14 good chromium@463605 --- --- build failure chromium@463606 --- --- build failure chromium@463607 --- --- build failure chromium@463608 --- --- build failure chromium@463609 --- --- build failure chromium@463610 --- --- build failure chromium@463611 --- --- build failure chromium@463612 --- --- build failure chromium@463613 31686111 +- 6846678 14 bad chromium@463638 31594119 +- 4011539 6 bad chromium@463672 30040983 +- 9318372 14 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=background.search.google system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982012718269304240 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5828354780954624 | 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!
,
Jul 19 2017
,
Jul 27 2017
This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by benhenry@google.com
, Apr 17 2017