Issue metadata
Sign in to add a comment
|
12% regression in system_health.memory_mobile at 462082:462192 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 19 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981887861227108864
,
Apr 19 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_news/browse_news_hackernews Revision Result N chromium@462081 24219805 +- 1902708 21 good chromium@462192 24312648 +- 0.0 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=browse.news.hackernews system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981887861227108864 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6713476136828928 | 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 19 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981869201006348256
,
Apr 19 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_news/browse_news_hackernews Revision Result N chromium@462081 24126963 +- 2622703 21 good chromium@462192 24219805 +- 1902708 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=browse.news.hackernews system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981869201006348256 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6713476136828928 | 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 20 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981766480854712592
,
Apr 20 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_news/browse_news_hackernews Revision Result N chromium@462081 24126963 +- 2622703 21 good chromium@462192 23941277 +- 3508421 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=browse.news.hackernews system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981766480854712592 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6713476136828928 | 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 21 2017
Looks like a false alert.
,
Apr 27 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981125434340531088
,
Apr 28 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_news/browse_news_hackernews Revision Result N chromium@462081 24219805 +- 1902708 21 good chromium@462192 24312648 +- 0.0 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=browse.news.hackernews system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981125434340531088 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6713476136828928 | 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 |
|||||||||||||||||||||
Comment 1 by alexclarke@chromium.org
, Apr 19 2017