Issue metadata
Sign in to add a comment
|
10.4%-55.9% regression in v8.browsing_desktop at 490645:490669 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8972474384329940384
,
Aug 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8972474348047163856
,
Aug 1 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Ulan Degenbaev Commit : 774a4c5e240569b551cc9d19ae8cac146891d4c4 Date : Fri Jul 28 19:42:31 2017 Subject: Revert "[heap] Reland "[heap] Allow a minimum semi-space size of 512K."" Bisect Details Configuration: winx64ati_perf_bisect Benchmark : v8.browsing_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_max/browse_search/browse_search_google_india Change : 15.05% | 18576725.3333 -> 21372928.0 Revision Result N chromium@490644 18576725 +- 1284238 9 good chromium@490652 18227200 +- 1284238 9 good chromium@490652,v8@59ddd6061c 18576725 +- 605396 6 good chromium@490652,v8@e567dd3ab4 18489344 +- 642119 6 good chromium@490652,v8@774a4c5e24 22421504 +- 0.0 6 bad <-- chromium@490652,v8@4a9718c777 21809835 +- 1878191 6 bad chromium@490653 21722453 +- 5397875 9 bad chromium@490654 22334123 +- 478607 6 bad chromium@490656 21635072 +- 3210595 6 bad chromium@490659 21372928 +- 3397775 6 bad 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=browse.search.google.india v8.browsing_desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8972474348047163856 For feedback, file a bug with component Speed>Bisection
,
Aug 1 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_perf_bisect Benchmark : v8.browsing_desktop Metric : v8-gc-scavenger_avg/browse_search/browse_search_google_india Change : 39.12% | 0.638399760331 -> 0.888146187364 Suspected Commit Range 2 commits in range https://chromium.googlesource.com/v8/v8.git/+log/e567dd3ab4b5ec1c72ff91716800b0fcdcd2c1b2..4a9718c7776b48deb4a49d66d5079f26a14c31c0 Revision Result N chromium@490644 0.6384 +- 0.516997 14 good chromium@490650 0.628984 +- 0.531369 14 good chromium@490652 0.578717 +- 0.474225 9 good chromium@490652,v8@59ddd6061c 0.581213 +- 0.439021 9 good chromium@490652,v8@e567dd3ab4 0.672768 +- 0.806403 14 good chromium@490652,v8@774a4c5e24 --- --- build failure chromium@490652,v8@4a9718c777 0.844019 +- 0.818042 14 bad chromium@490653 0.941206 +- 0.580307 6 bad chromium@490656 0.865643 +- 0.882689 14 bad chromium@490667 0.888146 +- 0.666258 9 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.search.google.india v8.browsing_desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8972474384329940384 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 1 2017