Issue metadata
Sign in to add a comment
|
3.8% regression in system_health.memory_desktop at 489865:489904 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 4 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8972178097372263424
,
Aug 4 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: win_8_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_games/load_games_alphabetty Change : 3.02% | 9097216.0 -> 8822588.95238 Suspected Commit Range 2 commits in range https://chromium.googlesource.com/chromium/src/+log/a34f8c0dd8413ae7f970d13267a09fe69e4819f0..6b8fafc58277a007a25257b4f763ad71fa89f06c Revision Result N chromium@489864 9097216 +- 0.0 21 good chromium@489884 9097216 +- 0.0 14 good chromium@489894 9097216 +- 0.0 14 good chromium@489897 9059767 +- 505217 14 good chromium@489898 --- --- build failure chromium@489899 8722725 +- 886208 14 bad chromium@489904 8822589 +- 1199932 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.games.alphabetty system_health.memory_desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8972178097372263424 For feedback, file a bug with component Speed>Bisection
,
Aug 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8971270355483057968
,
Aug 14 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: win_8_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_games/load_games_alphabetty Change : 4.80% | 9097216.0 -> 8797622.85714 Suspected Commit Range 2 commits in range https://chromium.googlesource.com/chromium/src/+log/a34f8c0dd8413ae7f970d13267a09fe69e4819f0..6b8fafc58277a007a25257b4f763ad71fa89f06c Revision Result N chromium@489864 9097216 +- 0.0 9 good chromium@489884 9097216 +- 0.0 9 good chromium@489894 9097216 +- 0.0 14 good chromium@489897 9059767 +- 505217 14 good chromium@489898 --- --- build failure chromium@489899 8772657 +- 1166748 21 bad chromium@489904 8797623 +- 970793 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.games.alphabetty system_health.memory_desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8971270355483057968 For feedback, file a bug with component Speed>Bisection
,
Aug 21 2017
Suspecting parallel scavenge. :)
,
Aug 21 2017
Thanks for checking. Closing because that is a trade off. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 4 2017