Issue metadata
Sign in to add a comment
|
4.5%-58.9% regression in v8.runtimestats.browsing_mobile at 477932:482515 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 30 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975382048078444944
,
Jun 30 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : v8.mobile_infinite_scroll_tbmv2 Metric : total:500ms_window:renderer_eqt:v8:gc:scavenger_max/total:500ms_window:renderer_eqt:v8:gc:scavenger_max Revision Result N chromium@481857 1.31498 +- 1.10791 21 good chromium@481918 1.23834 +- 0.864397 21 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 v8.mobile_infinite_scroll_tbmv2 More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8975382048078444944 For feedback, file a bug with component Speed>Bisection
,
Jun 30 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975350759302672416
,
Jul 1 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : v8.mobile_infinite_scroll_tbmv2 Metric : total:500ms_window:renderer_eqt:v8:gc:scavenger_max/total:500ms_window:renderer_eqt:v8:gc:scavenger_max Revision Result N chromium@481857 1.24544 +- 0.50778 21 good chromium@481918 1.38851 +- 1.51205 21 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 v8.mobile_infinite_scroll_tbmv2 More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8975350759302672416 For feedback, file a bug with component Speed>Bisection
,
Jul 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974468466091741792
,
Jul 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974468456089894432
,
Jul 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974468449995401328
,
Jul 10 2017
I kicked off more bisects. If they also fail, let's close this issue.
,
Jul 11 2017
,
Jul 11 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : v8.runtimestats.browsing_mobile Metric : V8 C++:duration_avg/browse_chrome/browse_chrome_newtab Revision Result N chromium@477935 1465.74 +- 195.824 14 good chromium@482515 2212.46 +- 272.841 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.chrome.newtab 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/8974468456089894432 For feedback, file a bug with component Speed>Bisection
,
Jul 11 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : v8.runtimestats.browsing_mobile Metric : JavaScript:duration_avg/browse_chrome/browse_chrome_newtab Revision Result N chromium@477931 2354.65 +- 65.748 10 good chromium@482487 3055.63 +- 116.436 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.chrome.newtab 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/8974468466091741792 For feedback, file a bug with component Speed>Bisection
,
Jul 11 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : v8.runtimestats.browsing_mobile Metric : Total:duration_avg/browse_chrome/browse_chrome_newtab Revision Result N chromium@477935 11646.9 +- 592.418 14 good chromium@482515 13858.9 +- 1598.54 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.chrome.newtab 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/8974468449995401328 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by bmeu...@chromium.org
, Jun 30 2017