Issue metadata
Sign in to add a comment
|
1.1%-3.1% regression in memory.top_10_mobile at 447955:447999 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 8 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988183041250499744
,
Feb 9 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/foreground/https_m_facebook_com_rihanna Revision Result N chromium@447954 49187652 +- 3447210 21 good chromium@447998 48978366 +- 3185135 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 memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8988183041250499744 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5549454985265152 | 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!
,
Feb 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988006317339480448
,
Feb 11 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/foreground/https_m_facebook_com_rihanna Revision Result N chromium@447954 49042926 +- 2920190 21 good chromium@447998 48958081 +- 2681525 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 memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8988006317339480448 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6426450095243264 | 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!
,
Mar 11 2017
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982611974535536448
,
Apr 11 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/foreground/https_m_facebook_com_rihanna Revision Result N chromium@447954 49187652 +- 3447210 21 good chromium@447998 48978366 +- 3185135 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 memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982611974535536448 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5549454985265152 | 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 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 briander...@chromium.org
, Feb 8 2017