Issue metadata
Sign in to add a comment
|
321.9% regression in v8.browsing_mobile at 496048:496667 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 25 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8970304232071206320
,
Aug 25 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_nexus7_perf_bisect Benchmark : v8.browsing_mobile Metric : v8-gc-total_max/browse_social/browse_social_instagram Change : 127.12% | 27.83 -> 63.2087777778 Suspected Commit Range 7 commits in range https://chromium.googlesource.com/chromium/src/+log/f4b6de131ff7e248b4404d7cca45c14a7ccf1441..0a7aafaae4eb1d726d7564d4d63960a73c36594d Revision Result N chromium@496047 27.83 +- 60.9211 14 good chromium@496203 23.2761 +- 39.0343 14 good chromium@496205 24.7649 +- 36.034 14 good chromium@496206 --- --- build failure chromium@496207 --- --- build failure chromium@496208 --- --- build failure chromium@496209 --- --- build failure chromium@496210 --- --- build failure chromium@496211 --- --- build failure chromium@496212 30.9754 +- 66.3272 14 bad chromium@496221 41.628 +- 93.0799 14 bad chromium@496242 64.5412 +- 50.9483 9 bad chromium@496280 45.2031 +- 96.3087 14 bad chromium@496357 61.4299 +- 87.8317 14 bad chromium@496667 63.2088 +- 62.045 9 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.social.instagram 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/8970304232071206320 For feedback, file a bug with component Speed>Bisection
,
Aug 28 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8970016250251925728
,
Aug 28 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_nexus7_perf_bisect Benchmark : v8.browsing_mobile Metric : v8-gc-total_max/browse_social/browse_social_instagram Change : 172.12% | 27.5399285714 -> 55.6618571429 Suspected Commit Range 2 commits in range https://chromium.googlesource.com/chromium/src/+log/10c49d72428d58647f5f73712edcd2c40b3169ab..6a2d24e5e5ab0b657f3740856c37b73b914d55e1 Revision Result N chromium@496000 27.5399 +- 35.6708 14 good chromium@496175 21.5505 +- 13.1234 6 good chromium@496219 24.3159 +- 32.7533 14 good chromium@496226 27.6142 +- 54.8823 14 good chromium@496228 22.4545 +- 24.2631 14 good chromium@496229 --- --- build failure chromium@496230 59.3065 +- 90.7654 14 bad chromium@496241 60.8454 +- 68.2244 9 bad chromium@496262 69.9617 +- 2.51547 6 bad chromium@496349 73.5118 +- 5.94971 6 bad chromium@496699 55.6619 +- 93.2238 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.social.instagram 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/8970016250251925728 For feedback, file a bug with component Speed>Bisection
,
Sep 10
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 25 2017