Issue metadata
Sign in to add a comment
|
9.6%-166.2% regression in loading.desktop at 504628:504874 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8966741005645811088
,
Oct 3 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_10_11_perf_bisect Benchmark : loading.desktop Metric : cpuTimeToFirstMeaningfulPaint_avg/warm/Economist Revision Result N chromium@504734 436.182 +- 456.974 21 good chromium@504807 433.47 +- 439.142 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=Economist loading.desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8966741005645811088 For feedback, file a bug with component Speed>Bisection
,
Dec 12 2017
Bisect unable to find culprit, this regression exists in stable. Ignoring. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 3 2017