Issue metadata
Sign in to add a comment
|
11.4%-21914.6% regression in loading.mobile at 515646:515819 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8963037102813268752
,
Nov 13 2017
Revert of recent improvement.
,
Nov 13 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Caleb Rouleau Commit : 46cf2b51bb3b56831ded3ffb60400f51091400ea Date : Fri Nov 10 22:23:42 2017 Subject: [Telemetry] give traffic_setting to parent. Fix Bug. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : loading.mobile Metric : timeToFirstContentfulPaint_avg/cold_Regular-3G/FlipBoard Change : 29678.65% | 167.7435 -> 49951.7556667 Revision Result N chromium@515681 167.743 +- 53.155 6 good chromium@515711 162.788 +- 51.4696 6 good chromium@515713 163.816 +- 52.1667 6 good chromium@515714 49831.8 +- 462.523 6 bad <-- chromium@515715 49545.4 +- 1032.97 6 bad chromium@515719 49432.9 +- 1167.88 6 bad chromium@515726 49558.3 +- 1008.4 6 bad chromium@515740 49728.9 +- 1585.34 6 bad chromium@515799 49951.8 +- 794.304 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=FlipBoard loading.mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8963037102813268752 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 13 2017