Issue metadata
Sign in to add a comment
|
1.2%-250.3% regression in v8.runtimestats.browsing_desktop at 486026:486321 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 18 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8973748652176442160
,
Jul 18 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: linux_perf_bisect Benchmark : v8.runtimestats.browsing_desktop Metric : v8-gc-scavenger_max/browse_social/browse_social_twitter Revision Result N chromium@486045 9.86162 +- 3.92461 21 good chromium@486135 9.71376 +- 3.41989 21 bad 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.social.twitter v8.runtimestats.browsing_desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8973748652176442160 For feedback, file a bug with component Speed>Bisection
,
Jul 25 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8973112152994631952
,
Jul 25 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8973112121141848208
,
Jul 25 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8973112100676061312
,
Jul 25 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Camillo Bruni Commit : 36421dc467bffcdcb71967ed39dddca1e33d48c6 Date : Wed Jul 12 19:11:04 2017 Subject: [literals] Disable double lazy boilerplate for literals containing Arrays 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_google Change : 5.64% | 11335366.6667 -> 11975146.6667 Revision Result N chromium@486050 11335367 +- 202659 6 good chromium@486193 11369424 +- 207228 6 good chromium@486229 11344668 +- 170190 6 good chromium@486247 11403823 +- 190302 6 good chromium@486248 11377075 +- 211839 6 good chromium@486248,v8@42c8df3f46 11365115 +- 204505 6 good chromium@486248,v8@34874b3b19 11333716 +- 217139 6 good chromium@486248,v8@36421dc467 11967703 +- 222398 6 bad <-- chromium@486248,v8@fa4ec9fdbe 11924855 +- 135931 6 bad chromium@486249 12024487 +- 275590 6 bad chromium@486250 12042513 +- 141709 6 bad chromium@486252 12005895 +- 193381 6 bad chromium@486256 11956860 +- 179638 6 bad chromium@486264 12012277 +- 181456 6 bad chromium@486335 11975147 +- 235519 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.search.google 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/8973112121141848208 For feedback, file a bug with component Speed>Bisection
,
Jul 25 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Camillo Bruni Commit : 36421dc467bffcdcb71967ed39dddca1e33d48c6 Date : Wed Jul 12 19:11:04 2017 Subject: [literals] Disable double lazy boilerplate for literals containing Arrays Bisect Details Configuration: mac_10_12_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/load_search/load_search_google Change : 5.96% | 10456770.6667 -> 11080456.0 Revision Result N chromium@486050 10456771 +- 2112.63 6 good chromium@486193 10456437 +- 1126.99 6 good chromium@486229 10456981 +- 1102.88 6 good chromium@486247 10456940 +- 1650.24 6 good chromium@486248 10456709 +- 1492.32 6 good chromium@486248,v8@42c8df3f46 10456788 +- 1773.83 6 good chromium@486248,v8@34874b3b19 10456397 +- 1202.27 6 good chromium@486248,v8@36421dc467 11080707 +- 1309.54 6 bad <-- chromium@486248,v8@fa4ec9fdbe 11080293 +- 860.04 6 bad chromium@486249 11080648 +- 1110.59 6 bad chromium@486250 11080811 +- 1889.82 6 bad chromium@486252 11081008 +- 1718.31 6 bad chromium@486256 11080661 +- 1643.75 6 bad chromium@486264 11081051 +- 1371.23 6 bad chromium@486335 11080456 +- 1287.53 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.search.google 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/8973112100676061312 For feedback, file a bug with component Speed>Bisection
,
Jul 25 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Camillo Bruni Commit : 36421dc467bffcdcb71967ed39dddca1e33d48c6 Date : Wed Jul 12 19:11:04 2017 Subject: [literals] Disable double lazy boilerplate for literals containing Arrays Bisect Details Configuration: win_8_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_media/browse_media_flickr_infinite_scroll Change : 3.31% | 17674660.0 -> 18259621.3333 Revision Result N chromium@486225 17674660 +- 52232.5 6 good chromium@486242 17676741 +- 41206.4 6 good chromium@486247 17670708 +- 75972.3 6 good chromium@486248 17686729 +- 42353.6 6 good chromium@486248,v8@42c8df3f46 17671267 +- 24196.1 6 good chromium@486248,v8@34874b3b19 17693832 +- 61070.3 6 good chromium@486248,v8@36421dc467 18261463 +- 53456.8 6 bad <-- chromium@486248,v8@fa4ec9fdbe 18235173 +- 68517.6 6 bad chromium@486249 18256384 +- 140152 6 bad chromium@486251 18245465 +- 76158.3 6 bad chromium@486259 18252241 +- 93116.1 6 bad chromium@486293 18242184 +- 42539.2 6 bad chromium@486360 18259621 +- 64197.4 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=browse.media.flickr.infinite.scroll 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/8973112152994631952 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 18 2017