Issue metadata
Sign in to add a comment
|
4.1% regression in loading.desktop at 507163:507663 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 31 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8964186751566946192
,
Oct 31 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: win_x64_perf_bisect Benchmark : loading.desktop Metric : timeToFirstMeaningfulPaint_avg/cold/FIFA Revision Result N chromium@507162 1079.17 +- 2735.12 21 good chromium@507663 935.086 +- 110.607 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=FIFA loading.desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8964186751566946192 For feedback, file a bug with component Speed>Bisection
,
Jan 11 2018
Seems a return to previous levels, and bisect can't repro. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 31 2017