Issue metadata
Sign in to add a comment
|
2% regression in memory.top_10_mobile_stress at 447213:447225 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 8 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988183529364419440
,
Feb 9 2017
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2971 Failure reason: the build has failed due to infrastructure failure.
,
Feb 9 2017
,
Feb 9 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988111993003960304
,
Feb 9 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988111972696031792
,
Feb 9 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988111929488846784
,
Feb 9 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : memory.top_10_mobile_stress Metric : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_yandex_ru_touchsearch_text_science Revision Result N chromium@447212 10533235 +- 687099 21 good chromium@447225 10493099 +- 918267 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_stress Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8988111972696031792 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5515178193453056 | 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!
,
Feb 10 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_nexus6_perf_bisect Benchmark : memory.top_10_mobile_stress Metric : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_yandex_ru_touchsearch_text_science Change : 0.09% | 10506030.0952 -> 10515906.4762 Suspected Commit Range 3 commits in range https://chromium.googlesource.com/chromium/src/+log/f7b320544b2f99fe301308420efdb1acf0196838..ed317bdc0d772dda0fb183d1b306131cd317b937 Revision Result N chromium@447212 10506030 +- 796566 21 good chromium@447213 10580026 +- 35524.7 14 good chromium@447213,v8@daad4319c9 --- --- build failure chromium@447213,v8@d224e4e7dc --- --- build failure chromium@447214 10553008 +- 501324 14 bad chromium@447216 10534196 +- 491150 9 bad chromium@447219 10528584 +- 488549 9 bad chromium@447225 10515906 +- 832673 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_stress Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8988111993003960304 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5055795034587136 | 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!
,
Feb 10 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : jkummerow Commit : daad4319c960b714c270b2c603b1f03bbc6ade14 Date : Tue Jan 31 06:41:14 2017 Subject: Put ThinStrings behind a flag (off by default) Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : memory.top_10_mobile_stress Metric : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_yandex_ru_touchsearch_text_science Change : 0.10% | 10545852.0 -> 10555922.5714 Revision Result N chromium@447212 10545852 +- 466602 14 good chromium@447213 10543043 +- 482735 14 good chromium@447213,v8@daad4319c9 10593584 +- 23734.5 6 bad <-- chromium@447213,v8@d224e4e7dc 10515583 +- 823334 21 bad chromium@447214 10591073 +- 38754.5 14 bad chromium@447217 10551865 +- 491709 14 bad chromium@447225 10555923 +- 499990 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 memory.top_10_mobile_stress Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8988111929488846784 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6341404273410048 | 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
,
Mar 11 2017
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982612107585303808
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982611840162673472 |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by briander...@chromium.org
, Feb 8 2017