Issue metadata
Sign in to add a comment
|
9.2% regression in loading.mobile at 510648:510674 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 23 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8964935251657469184
,
Oct 23 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : loading.mobile Metric : cpuTimeToFirstMeaningfulPaint_avg/Regular-3G/GoogleIndonesia Revision Result N chromium@510647 384.98 +- 99.0382 21 good chromium@510674 388.726 +- 106.924 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=GoogleIndonesia loading.mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8964935251657469184 For feedback, file a bug with component Speed>Bisection
,
Jan 8 2018
This came back down. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 23 2017