Issue metadata
Sign in to add a comment
|
84.2% regression in v8.browsing_mobile at 499261:499388 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 4 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8969399436877680608
,
Sep 4 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: android_nexus5X_perf_bisect Benchmark : v8.browsing_mobile Metric : v8-gc-incremental-step_max/browse_tech/browse_tech_discourse_infinite_scroll Change : 130.49% | 1.94564285714 -> 4.29633333333 Suspected Commit Range 3 commits in range https://chromium.googlesource.com/chromium/src/+log/6122d4c46b0e6c57d77f180083d57fbf78dd2d1a..0ca61beb9b0295961d963450dbea5fc021e7fa18 Revision Result N chromium@499260 1.94564 +- 0.678154 14 good chromium@499261 2.01478 +- 0.620559 9 good chromium@499262 --- --- build failure chromium@499263 --- --- build failure chromium@499264 2.22379 +- 0.890178 14 bad chromium@499268 3.14917 +- 1.16167 6 bad chromium@499276 3.4285 +- 0.689402 6 bad chromium@499292 3.55033 +- 0.306675 6 bad chromium@499324 3.55617 +- 0.619213 6 bad chromium@499388 4.29633 +- 2.5449 6 bad 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=browse.tech.discourse.infinite.scroll v8.browsing_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8969399436877680608 For feedback, file a bug with component Speed>Bisection
,
Sep 4 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8969378192591789696
,
Sep 4 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: android_nexus5X_perf_bisect Benchmark : v8.browsing_mobile Metric : v8-gc-incremental-step_max/browse_tech/browse_tech_discourse_infinite_scroll Change : 93.86% | 2.46477777778 -> 4.92866666667 Suspected Commit Range 2 commits in range https://chromium.googlesource.com/v8/v8.git/+log/c58460b25f69acb2250d1d34af022de8b6c76bd6..70a516387a159a82f4b7dd6277ad26ee7e022519 Revision Result N chromium@499260 2.46478 +- 0.598356 9 good chromium@499264 2.66633 +- 1.4988 9 good chromium@499265 2.421 +- 0.974001 9 good chromium@499265,v8@ece1e2d149 2.33179 +- 1.13489 14 good chromium@499265,v8@c58460b25f 2.50586 +- 2.15531 14 good chromium@499265,v8@68eabceb15 --- --- build failure chromium@499265,v8@70a516387a 3.14429 +- 1.42566 14 bad chromium@499265,v8@36ef81b6ea 3.00992 +- 1.40777 13 bad chromium@499265,v8@9619b7f23c 3.25011 +- 2.31825 9 bad chromium@499265,v8@d138f8d7ef 3.6185 +- 0.870968 6 bad chromium@499266 3.493 +- 0.790243 9 bad chromium@499268 3.465 +- 0.684446 9 bad chromium@499276 3.4575 +- 0.609744 6 bad chromium@499292 3.56167 +- 0.991249 6 bad chromium@499324 3.39817 +- 0.481638 6 bad chromium@499388 4.92867 +- 2.09105 6 bad 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=browse.tech.discourse.infinite.scroll v8.browsing_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8969378192591789696 For feedback, file a bug with component Speed>Bisection
,
Sep 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8969306371534132896
,
Sep 5 2017
=== Auto-CCing suspected CL author jgruber@chromium.org === Hi jgruber@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : jgruber Commit : 70a516387a159a82f4b7dd6277ad26ee7e022519 Date : Wed Aug 30 09:46:40 2017 Subject: Reland "[snapshot] Move builtins to dedicated snapshot area" Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : v8.browsing_mobile Metric : v8-gc-incremental-step_max/browse_tech/browse_tech_discourse_infinite_scroll Change : 36.63% | 2.46666666667 -> 3.37016666667 Revision Result N chromium@499261 2.46667 +- 1.01218 6 good chromium@499265 2.52164 +- 1.53271 14 good chromium@499265,v8@ece1e2d149 2.48167 +- 0.596742 6 good chromium@499265,v8@68eabceb15 2.37883 +- 0.589416 6 good chromium@499265,v8@70a516387a 3.36583 +- 0.866336 6 bad <-- chromium@499265,v8@36ef81b6ea 3.38683 +- 1.23902 6 bad chromium@499265,v8@9619b7f23c 3.10889 +- 0.665534 9 bad chromium@499265,v8@d138f8d7ef 3.00964 +- 1.34484 14 bad chromium@499266 3.38178 +- 1.10768 9 bad chromium@499267 3.30867 +- 0.668329 6 bad chromium@499269 3.24678 +- 0.829386 9 bad chromium@499276 3.37017 +- 0.190842 6 bad 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=browse.tech.discourse.infinite.scroll v8.browsing_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8969306371534132896 For feedback, file a bug with component Speed>Bisection
,
Sep 5 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 4 2017