Issue metadata
Sign in to add a comment
|
1.2% regression in memory.top_10_mobile at 446258:446284 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 31 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988937177436845072
,
Jan 31 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science Revision Result N chromium@446257 45843946 +- 1213784 21 good chromium@446284 45657871 +- 970906 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=http.en.m.wikipedia.org.wiki.Science memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8988937177436845072 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5577554070601728 | 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 17 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8987399401674707072
,
Feb 17 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science Revision Result N chromium@446257 52425150 +- 2526079 21 good chromium@446284 52379265 +- 2792492 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/8987399401674707072 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6107923710738432 | 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/8982611887355042304
,
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 pmeenan@chromium.org
, Jan 31 2017