Issue metadata
Sign in to add a comment
|
21.9%-170.5% regression in loading.desktop at 494005:494032 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8971091479905442384
,
Aug 16 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_retina_perf_bisect Benchmark : loading.desktop Metric : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/Baidu Revision Result N chromium@494009 86.1917 +- 142.252 21 good chromium@494032 79.5681 +- 128.849 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=Baidu loading.desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8971091479905442384 For feedback, file a bug with component Speed>Bisection
,
Sep 21 2017
This recovered. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 16 2017