Issue metadata
Sign in to add a comment
|
2.7% regression in system_health.memory_mobile at 444018:444070 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 20 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8989962834271754832
,
Jan 20 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8989962807099191888
,
Jan 21 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_nexus9_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg Suspected Commit Range 53 commits in range https://chromium.googlesource.com/chromium/src/+log/e44e863e19ffca8ed95c0e395641ed1679482d12..a247cc78340405414f9ed1085976abc611ab2d1a Revision Result N chromium@444017 14979847 +- 132516 6 good chromium@444018 --- --- build failure --- --- --- too many build failures to list chromium@444069 --- --- build failure chromium@444070 15247409 +- 211766 6 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 system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8989962834271754832 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5801268733280256 | 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 21 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_nexus9_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:v8:heap:code_space:allocated_objects_size_avg/memory:chrome:all_processes:reported_by_chrome:v8:heap:code_space:allocated_objects_size_avg Suspected Commit Range 53 commits in range https://chromium.googlesource.com/chromium/src/+log/e44e863e19ffca8ed95c0e395641ed1679482d12..a247cc78340405414f9ed1085976abc611ab2d1a Revision Result N chromium@444017 3162132 +- 247406 9 good chromium@444018 --- --- build failure --- --- --- too many build failures to list chromium@444069 --- --- build failure chromium@444070 3398297 +- 147824 6 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 system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8989962807099191888 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5905689857228800 | 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 23 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8989671103609656624
,
Jan 23 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8989671091441468352
,
Jan 23 2017
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/7118 Failure reason: the build has failed due to infrastructure failure.
,
Jan 23 2017
=== BISECT JOB RESULTS === Perf regression found but unable to continue Bisect was stopped because a commit couldn't be classified as either good or bad. Bisect Details Configuration: win_8_perf_bisect Benchmark : v8.browsing_desktop Metric : v8-gc-incremental-step_sum/browse_search/browse_search_google_india To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.search.google.india v8.browsing_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8989671091441468352 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5879579006205952 | 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 23 2017
,
Jan 23 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8989667174664867632
,
Jan 23 2017
Bisect failed: None Failure reason: the build has failed due to infrastructure failure.
,
Apr 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982667505269848000
,
Apr 11 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: winx64ati_perf_bisect Benchmark : v8.browsing_desktop Metric : v8-gc-incremental-step_sum/browse_search/browse_search_google_india Revision Result N chromium@444018 31.8849 +- 9.43608 21 good chromium@444039 31.5526 +- 6.97998 14 good chromium@444042 31.5153 +- 7.12829 14 good chromium@444043 31.8639 +- 6.61198 14 good chromium@444043,v8@68c994795e 34.7948 +- 3.08519 6 bad chromium@444044 33.9797 +- 5.92368 14 bad chromium@444049 34.0957 +- 6.28582 14 bad chromium@444059 34.0294 +- 4.48707 14 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.search.google.india v8.browsing_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982667505269848000 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4953966443495424 | 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 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982580381209577520
,
Apr 11 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_nexus9_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg Suspected Commit Range 53 commits in range https://chromium.googlesource.com/chromium/src/+log/e44e863e19ffca8ed95c0e395641ed1679482d12..a247cc78340405414f9ed1085976abc611ab2d1a Revision Result N chromium@444017 14979847 +- 132516 6 good chromium@444018 --- --- build failure --- --- --- too many build failures to list chromium@444069 --- --- build failure chromium@444070 15247409 +- 211766 6 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 system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982580381209577520 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5801268733280256 | 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 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982536522737872096
,
Apr 12 2017
The benchmark seems to not have any new data after 01/21. I kicked off another bisect since it would still be interesting to see what caused the regression. The subset that regresses is load_news.
,
Apr 12 2017
=== BISECT JOB RESULTS === NO Perf regression found, tests failed to produce values Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/load_news 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=load_news system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982536522737872096 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5826474780655616 | 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!
,
Aug 22 2017
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by mlippautz@chromium.org
, Jan 20 2017