Issue metadata
Sign in to add a comment
|
4.6%-900.3% regression in v8.runtimestats.browsing_desktop at 489882:490179 |
||||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8972282879566699488
,
Aug 3 2017
=== BISECT JOB RESULTS === Perf regression found but unable to continue Bisect was stopped because a commit couldn't be classified as either good or bad. Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : v8.runtimestats.browsing_mobile Metric : Optimize:duration_avg/browse_news/browse_news_qq Revision Result N chromium@489964 14.5647 +- 22.6038 21 good chromium@490019 17.8118 +- 27.1156 21 unknown chromium@490074 18.8275 +- 20.4027 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.news.qq v8.runtimestats.browsing_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8972282879566699488 For feedback, file a bug with component Speed>Bisection
,
Aug 22 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8970554650740542528
,
Aug 22 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8970554637628732208
,
Aug 22 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : v8.runtimestats.browsing_mobile Metric : JavaScript:duration_avg/browse_news/browse_news_cricbuzz 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.news.cricbuzz v8.runtimestats.browsing_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8970554650740542528 For feedback, file a bug with component Speed>Bisection
,
Aug 22 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Michael Hablich Commit : 9bac201e0e32f198064a10c3032dbd839e8e8efd Date : Thu Jul 27 07:10:02 2017 Subject: Version 6.2.52.1 (cherry-pick) Bisect Details Configuration: winx64ati_perf_bisect Benchmark : v8.runtimestats.browsing_desktop Metric : v8-gc-memory-mark-compactor_sum/browse_social/browse_social_twitter_infinite_scroll Change : 135.21% | 16.7795 -> 39.4663333333 Revision Result N chromium@489889 16.7795 +- 3.70744 6 good chromium@489897 13.2288 +- 5.65523 6 good chromium@489897,v8@9bac201e0e 35.9067 +- 2.97127 6 bad <-- chromium@489898 38.5133 +- 6.17621 6 bad chromium@489899 34.7795 +- 4.76303 6 bad chromium@489901 34.667 +- 1.96185 6 bad chromium@489905 38.7563 +- 14.9648 6 bad chromium@489921 40.4583 +- 9.29903 6 bad chromium@489952 39.4663 +- 17.8017 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.social.twitter.infinite.scroll v8.runtimestats.browsing_desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8970554637628732208 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 3 2017