Issue metadata
Sign in to add a comment
|
1% regression in system_health.memory_desktop at 470447:470531 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 22 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978900449418729568
,
May 23 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: mac_retina_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_social 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=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests system_health.memory_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978900449418729568 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5905877380366336 | 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!
,
May 23 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978808731854426096
,
May 25 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: mac_retina_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_social 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=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests system_health.memory_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978808731854426096 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5905877380366336 | 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!
,
Jun 2 2017
,
Jun 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977889351165539456
,
Jun 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977889180790596752
,
Jun 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977889155995081664
,
Jun 2 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_10_12_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_search/load_search_taobao Revision Result N chromium@470444 12596381 +- 9217999 21 good chromium@470494 14212016 +- 1333537 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=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.search.taobao system_health.memory_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977889155995081664 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4929477726961664 | 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!
,
Jun 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977883889787015440
,
Jun 2 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : yhirano Commit : 91088a195969f5af61f404c9f02edc622cbe373a Date : Wed May 10 05:49:31 2017 Subject: Add Field Trial Testing Configuration for MojoLoading Bisect Details Configuration: mac_retina_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_social/load_social_facebook Change : 4.38% | 23734621.3333 -> 24773448.0 Revision Result N chromium@470446 23734621 +- 508897 6 good chromium@470484 23784080 +- 274735 6 good chromium@470489 23824243 +- 410189 6 good chromium@470490 24801412 +- 354116 6 bad <-- chromium@470491 24721253 +- 304067 6 bad chromium@470492 24636235 +- 151299 6 bad chromium@470494 24713568 +- 324763 6 bad chromium@470503 24801001 +- 68555.3 6 bad chromium@470521 24773448 +- 373356 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=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.social.facebook system_health.memory_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977889351165539456 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5770873295863808 | 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!
,
Jun 2 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_10_12_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_search/load_search_taobao Revision Result N chromium@470444 12552798 +- 9088023 21 good chromium@470494 14220988 +- 1203916 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=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.search.taobao system_health.memory_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977883889787015440 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4929477726961664 | 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!
,
Jun 2 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : yhirano Commit : 91088a195969f5af61f404c9f02edc622cbe373a Date : Wed May 10 05:49:31 2017 Subject: Add Field Trial Testing Configuration for MojoLoading Bisect Details Configuration: mac_air_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_search/load_search_taobao Change : 13.05% | 12307639.2381 -> 13913752.0 Revision Result N chromium@470444 12307639 +- 8318118 21 good chromium@470475 11961330 +- 8445271 21 good chromium@470483 11859212 +- 5334498 9 good chromium@470487 12303939 +- 6775966 14 good chromium@470489 12569111 +- 6616409 14 good chromium@470490 13980140 +- 703990 14 bad <-- chromium@470505 13913752 +- 273219 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=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.search.taobao system_health.memory_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977889180790596752 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5339383701438464 | 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!
,
Jun 2 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : yhirano Commit : 91088a195969f5af61f404c9f02edc622cbe373a Date : Wed May 10 05:49:31 2017 Subject: Add Field Trial Testing Configuration for MojoLoading Bisect Details Configuration: mac_air_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_search/load_search_taobao Change : 13.05% | 12307639.2381 -> 13913752.0 Revision Result N chromium@470444 12307639 +- 8318118 21 good chromium@470475 11961330 +- 8445271 21 good chromium@470483 11859212 +- 5334498 9 good chromium@470487 12303939 +- 6775966 14 good chromium@470489 12569111 +- 6616409 14 good chromium@470490 13980140 +- 703990 14 bad <-- chromium@470505 13913752 +- 273219 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=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.search.taobao system_health.memory_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977889180790596752 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5339383701438464 | 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! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by jochen@chromium.org
, May 22 2017