Issue metadata
Sign in to add a comment
|
13.2%-53.9% regression in v8.runtimestats.browsing_desktop at 476612:476890 |
||||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976800511110869552
,
Jun 14 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: win_x64_perf_bisect Benchmark : v8.runtimestats.browsing_desktop Metric : GC:duration_avg/browse_search/browse_search_google_india Revision Result N chromium@476611 12.6989 +- 7.42418 21 good chromium@476884 12.4497 +- 11.3093 21 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.runtimestats.browsing_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976800511110869552 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5777075799064576 | 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 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976789173553592272
,
Jun 15 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_x64_perf_bisect Benchmark : v8.runtimestats.browsing_desktop Metric : GC:duration_avg/browse_search/browse_search_google_india Change : 13.03% | 12.3437142857 -> 13.6167857143 Suspected Commit Range 6 commits in range https://chromium.googlesource.com/chromium/src/+log/15e1023261ee539b7d0037c2bb57596b48ca3ae3..420f4637737c8a0232941c7099b8b9bbb42b5fee Revision Result N chromium@476611 12.3437 +- 6.93925 14 good chromium@476748 12.3521 +- 7.72147 14 good chromium@476782 11.9904 +- 12.263 21 good chromium@476795 12.6864 +- 5.56029 14 good chromium@476803 12.6489 +- 5.46418 14 good chromium@476804 --- --- build failure chromium@476805 --- --- build failure chromium@476806 --- --- build failure chromium@476807 --- --- build failure chromium@476808 --- --- build failure chromium@476809 13.3998 +- 10.7092 21 bad chromium@476815 13.6995 +- 8.21145 14 bad chromium@476884 13.6168 +- 3.23435 14 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.runtimestats.browsing_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976789173553592272 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5777075799064576 | 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 15 2017
Assigning to performance sheriff.
,
Jun 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976647717736888064
,
Jun 17 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : hpayer Commit : 502c6ae6a03979efbd3e006e6a0b8c3369ca2bbc Date : Fri Jun 02 09:40:16 2017 Subject: [heap] Activate memory reducer on external memory activity. Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : v8.runtimestats.browsing_mobile_classic Metric : IC:duration_avg/browse_social/browse_social_instagram Change : 14.15% | 695.169666667 -> 793.546 Revision Result N chromium@476626 695.17 +- 37.4147 6 good chromium@476643 699.531 +- 28.7377 6 good chromium@476651 697.918 +- 37.0908 6 good chromium@476655 694.692 +- 23.9317 6 good chromium@476656 716.007 +- 48.6744 6 good chromium@476656,v8@d1a9603e57 704.781 +- 35.7169 6 good chromium@476656,v8@502c6ae6a0 806.193 +- 62.0362 6 bad <-- chromium@476656,v8@3b7ff7a5e5 793.261 +- 41.0388 6 bad chromium@476657 805.62 +- 38.6988 6 bad chromium@476659 793.358 +- 40.4438 6 bad chromium@476691 793.546 +- 45.5958 6 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.instagram v8.runtimestats.browsing_mobile_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976647717736888064 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5211834749026304 | 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! |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by tebbi@chromium.org
, Jun 14 2017