Issue metadata
Sign in to add a comment
|
46.8% improvement in v8.runtimestats.browsing_mobile at 470457:470497 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979537716805337680
,
May 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979537709590115120
,
May 16 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : yhirano Commit : 91088a195969f5af61f404c9f02edc622cbe373a Date : Wed May 10 05:49:31 2017 Subject: Add Field Trial Testing Configuration for MojoLoading Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : v8.runtimestats.browsing_mobile Metric : Parse-Background:duration_avg/browse_tools/browse_tools_maps Change : 41.99% | 113.328 -> 65.7455 Revision Result N chromium@470456 113.328 +- 62.6076 6 good chromium@470477 102.926 +- 28.3808 6 good chromium@470487 128.082 +- 70.9776 6 good chromium@470489 108.139 +- 25.6334 6 good chromium@470490 61.98 +- 8.86081 6 bad <-- chromium@470492 65.904 +- 8.824 6 bad chromium@470497 65.7455 +- 13.1415 6 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 --story-filter=browse.tools.maps v8.runtimestats.browsing_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979537709590115120 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5979522949709824 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
May 16 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : yhirano Commit : 91088a195969f5af61f404c9f02edc622cbe373a Date : Wed May 10 05:49:31 2017 Subject: Add Field Trial Testing Configuration for MojoLoading Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : v8.runtimestats.browsing_mobile Metric : Parse-Background:duration_avg/browse_tools/browse_tools_maps Change : 47.45% | 124.368 -> 65.3586666667 Revision Result N chromium@470456 124.368 +- 40.9063 6 good chromium@470477 126.116 +- 90.083 6 good chromium@470487 126.443 +- 43.9683 6 good chromium@470489 122.225 +- 62.2614 6 good chromium@470490 65.7603 +- 16.3977 6 bad <-- chromium@470492 66.8272 +- 12.7145 6 bad chromium@470497 65.3587 +- 16.2117 6 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 --story-filter=browse.tools.maps v8.runtimestats.browsing_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979537716805337680 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5092167808188416 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by yhirano@chromium.org
, May 15 2017