Issue metadata
Sign in to add a comment
|
1.7% regression in system_health.memory_desktop at 482217:482279 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 29 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_pro_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_media/load_media_imgur Revision Result N chromium@482216 48191044 +- 2178752 21 good chromium@482279 48049338 +- 1661650 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.media.imgur system_health.memory_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8975459446456661200 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5876406430466048 | 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 29 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975456456398188240
,
Jun 29 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_pro_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_media/load_media_imgur Revision Result N chromium@482216 48149351 +- 2200922 21 good chromium@482279 48064815 +- 1550958 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.media.imgur system_health.memory_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8975456456398188240 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5876406430466048 | 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 29 2017
+sullivan, +simonhatch: some of this bugs are missing the "link to graphs below" that should usually appear at comment #1 For this bug: https://chromeperf.appspot.com/group_report?bug_id=737922
,
Jun 29 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975452316229696464
,
Jun 29 2017
Re #5: monorail team is looking into the problem here: https://bugs.chromium.org/p/monorail/issues/detail?id=2837
,
Jun 29 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64ati_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_games/load_games_miniclip Revision Result N chromium@482239 233668991 +- 13313984 21 good chromium@482296 234983678 +- 12035648 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_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.games.miniclip system_health.memory_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8975452316229696464 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4956960333496320 | 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 29 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975445131792518048
,
Jun 29 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975441665661241728
,
Jun 29 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : perezju Commit : b4eb70c319cb0f38d1a7764e7d9fb56dc96f8bcf Date : Mon Jun 26 14:25:41 2017 Subject: [System Health] Extend dump time to 5 seconds Bisect Details Configuration: winx64ati_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_games/load_games_miniclip Change : 0.86% | 233201413.714 -> 235216463.667 Revision Result N chromium@482239 233201414 +- 8625518 21 good chromium@482268 232591135 +- 5620316 14 good chromium@482282 232914504 +- 6679498 14 good chromium@482282,catapult@b4eb70c319 235450794 +- 10047540 21 bad <-- chromium@482283 235406841 +- 8118659 14 bad chromium@482284 235547770 +- 6675687 14 bad chromium@482286 236211544 +- 13147099 14 bad chromium@482289 235734437 +- 7020676 14 bad chromium@482296 235216464 +- 12378525 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_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.games.miniclip 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/8975445131792518048 For feedback, file a bug with component Speed>Bisection
,
Jun 30 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: winx64ati_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:gpu_process:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_games/load_games_miniclip Change : 5.15% | 72140771.6667 -> 76154217.7778 Suspected Commit Range 30 commits in range https://chromium.googlesource.com/chromium/src/+log/2efa616e207873fdbbf1ae8f144d16708b4a0d62..eb709ae5b1db1b2e96d1d396b4f81c4f24fa6adf Revision Result N chromium@482175 72140772 +- 5589416 9 good chromium@482295 73634012 +- 6187273 14 good chromium@482296 --- --- build failure --- --- --- too many build failures to list chromium@482324 --- --- build failure chromium@482325 74343463 +- 5788101 14 bad chromium@482355 77365499 +- 5876217 9 bad chromium@482415 76154218 +- 4866925 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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.games.miniclip 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/8975441665661241728 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jun 29 2017