Issue metadata
Sign in to add a comment
|
106.9% regression in v8.browsing_mobile at 495293:495369 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 22 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8970576607422220016
,
Aug 22 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : v8.browsing_mobile Metric : v8-gc-latency-mark-compactor_sum/browse_shopping/browse_shopping_amazon Revision Result N chromium@495292 167.546 +- 175.273 21 good chromium@495369 176.607 +- 166.063 20 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.shopping.amazon 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/8970576607422220016 For feedback, file a bug with component Speed>Bisection
,
Aug 22 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8970554996642029408
,
Aug 23 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_nexus5_perf_bisect Benchmark : v8.browsing_mobile Metric : v8-gc-latency-mark-compactor_sum/browse_shopping/browse_shopping_amazon Change : 52.85% | 111.419214286 -> 170.307642857 Suspected Commit Range 4 commits in range https://chromium.googlesource.com/chromium/src/+log/77e51afdb6a5be984481131c40da7def92459167..78ab7a20a5d3a321ee8262b82970c08bf8bc894d Revision Result N chromium@495260 111.419 +- 68.389 14 good chromium@495262 112.582 +- 73.16 21 good chromium@495263 --- --- build failure chromium@495264 --- --- build failure chromium@495265 --- --- build failure chromium@495266 127.797 +- 33.3395 14 bad chromium@495275 159.914 +- 222.06 21 bad chromium@495290 188.062 +- 186.542 14 bad chromium@495320 184.216 +- 109.309 6 bad chromium@495380 170.308 +- 151.68 14 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.shopping.amazon 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/8970554996642029408 For feedback, file a bug with component Speed>Bisection
,
Aug 23 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8970459394292801488
,
Aug 23 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : v8.browsing_mobile Metric : v8-gc-latency-mark-compactor_sum/browse_shopping/browse_shopping_amazon Revision Result N chromium@495282 181.598 +- 189.872 21 good chromium@495385 163.911 +- 207.237 21 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.shopping.amazon 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/8970459394292801488 For feedback, file a bug with component Speed>Bisection
,
Aug 24 2017
Back to normal. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 22 2017