Issue metadata
Sign in to add a comment
|
21.7% regression in loading.desktop at 494346:494399 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 29 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8969913072878822176
,
Aug 29 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_10_11_perf_bisect Benchmark : loading.desktop Metric : cpuTimeToFirstMeaningfulPaint_avg/pcv1-cold/Bhaskar Revision Result N chromium@494345 164.652 +- 31.5365 21 good chromium@494399 165.61 +- 33.6431 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=Bhaskar loading.desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8969913072878822176 For feedback, file a bug with component Speed>Bisection
,
Oct 9 2017
Just one page/bot, bisect can't repro. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 29 2017