Issue metadata
Sign in to add a comment
|
1.5%-168% regression in system_health.memory_mobile at 514967:515167 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8963024652255586032
,
Nov 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8963024504634777296
,
Nov 13 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Justin Novosad Commit : 5b07996e178c5f4e153e771d48ab839867fa7440 Date : Wed Nov 08 23:26:00 2017 Subject: Reland: Refactor of Canvas2DLayerBridge resource model Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/load_tools/load_tools_dropbox Change : 168.00% | 1248312.0 -> 3345464.0 Revision Result N chromium@514966 1248312 +- 0.0 6 good chromium@514991 1248312 +- 0.0 6 good chromium@514997 1248312 +- 0.0 6 good chromium@515000 1248312 +- 0.0 6 good chromium@515001 3345464 +- 0.0 6 bad <-- chromium@515002 3345464 +- 0.0 6 bad chromium@515003 3345464 +- 0.0 6 bad chromium@515015 3345464 +- 0.0 6 bad chromium@515063 3345464 +- 0.0 6 bad chromium@515160 3345464 +- 0.0 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 --story-filter=load.tools.dropbox system_health.memory_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8963024652255586032 For feedback, file a bug with component Speed>Bisection
,
Nov 13 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Justin Novosad Commit : 5b07996e178c5f4e153e771d48ab839867fa7440 Date : Wed Nov 08 23:26:00 2017 Subject: Reland: Refactor of Canvas2DLayerBridge resource model Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_games/load_games_bubbles Change : 35.35% | 19371199.3333 -> 26219600.0 Revision Result N chromium@514966 19371199 +- 28149.3 6 good chromium@514991 19366060 +- 0.0 6 good chromium@514997 19366060 +- 0.0 6 good chromium@515000 19366060 +- 0.0 6 good chromium@515001 26219600 +- 0.0 6 bad <-- chromium@515002 26219600 +- 0.0 6 bad chromium@515003 26219600 +- 0.0 6 bad chromium@515015 26224739 +- 28149.3 6 bad chromium@515063 26219600 +- 0.0 6 bad chromium@515160 26219600 +- 0.0 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 --story-filter=load.games.bubbles system_health.memory_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8963024504634777296 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 13 2017