Issue metadata
Sign in to add a comment
|
1.8% regression in memory.top_10_mobile at 442423:442467 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8990565145494573424
,
Jan 13 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_chrome:v8:effective_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science Revision Result N chromium@442423 7237735 +- 78109.7 21 good chromium@442467 7227170 +- 63561.6 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/8990565145494573424 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5238897895800832 | 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!
,
Jan 20 2017
,
Jan 24 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8989548204010584624
,
Jan 25 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : mvstanton Commit : 38602f1ff553b32815d34a05cd6d965f4fc20960 Date : Mon Jan 09 15:31:00 2017 Subject: [FeedbackVector] Infrastructure for literal arrays in the vector. Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science Change : 1.98% | 7198326.0 -> 7340797.77778 Revision Result N chromium@442191 7198326 +- 285276 14 good chromium@442278 7203965 +- 275608 14 good chromium@442300 7164087 +- 60992.3 9 good chromium@442311 7189145 +- 239024 14 good chromium@442312 7206031 +- 316885 14 good chromium@442312,v8@e7fc42796c 7199085 +- 274368 14 good chromium@442312,v8@38602f1ff5 7305278 +- 235391 14 bad <-- chromium@442313 7324051 +- 186017 6 bad chromium@442314 7306176 +- 136028 6 bad chromium@442317 7279599 +- 60755.0 9 bad chromium@442322 7312946 +- 186086 9 bad chromium@442365 7322432 +- 221236 9 bad chromium@442539 7340798 +- 108902 9 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/8989548204010584624 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4551925694988288 | 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!
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982651505262784160 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nzolghadr@chromium.org
, Jan 13 2017