Issue metadata
Sign in to add a comment
|
1.1%-24.8% regression in system_health.common_mobile at 476908:483326 |
||||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974917652525162560
,
Jul 6 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.common_mobile Metric : after_load:power_avg/load_games/load_games_bubbles 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=load.games.bubbles system_health.common_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8974917652525162560 For feedback, file a bug with component Speed>Bisection
,
Jul 6 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974811446036221328
,
Jul 6 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974811419475916384
,
Jul 6 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : tzik Commit : 211d6bc6aacfeed4aa730418801c86c7cef6719c Date : Thu Jun 29 04:19:13 2017 Subject: Notify RendererScheduler of starting LOADING phase on DidStartProvisionalLoad Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : system_health.common_mobile Metric : cpu_time_percentage_avg/browse_shopping/browse_shopping_amazon Change : 7.63% | 0.993230055124 -> 1.06899634307 Revision Result N chromium@483182 0.99323 +- 0.0119165 6 good chromium@483247 0.99704 +- 0.0133875 6 good chromium@483279 1.00108 +- 0.0111462 6 good chromium@483287 1.00054 +- 0.0124488 6 good chromium@483291 0.997622 +- 0.0234528 6 good chromium@483293 0.998218 +- 0.0248118 6 good chromium@483294 0.998451 +- 0.0122063 6 good chromium@483295 1.06899 +- 0.0220493 6 bad <-- chromium@483311 1.069 +- 0.010498 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.shopping.amazon system_health.common_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8974811446036221328 For feedback, file a bug with component Speed>Bisection
,
Jul 6 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : tzik Commit : 211d6bc6aacfeed4aa730418801c86c7cef6719c Date : Thu Jun 29 04:19:13 2017 Subject: Notify RendererScheduler of starting LOADING phase on DidStartProvisionalLoad Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : system_health.common_mobile Metric : cpu_time_percentage_avg/browse_social/browse_social_facebook Change : 11.37% | 0.527797595462 -> 0.587819487017 Revision Result N chromium@483279 0.527798 +- 0.0179566 6 good chromium@483292 0.532575 +- 0.0102945 6 good chromium@483294 0.530827 +- 0.00606226 6 good chromium@483295 0.587344 +- 0.0150526 6 bad <-- chromium@483298 0.585211 +- 0.0136256 6 bad chromium@483304 0.587819 +- 0.016874 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.social.facebook system_health.common_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8974811419475916384 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by rmcilroy@chromium.org
, Jul 5 2017