Issue metadata
Sign in to add a comment
|
18.2% improvement in speedometer2 at 504252:504455 |
||||||||||||||||||||||
Issue descriptionThis bump also affected the reference build.
,
Oct 4 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8966642506978566688
,
Oct 4 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: linux_perf_bisect Benchmark : speedometer2 Metric : Inferno-TodoMVC/Speedometer2 Revision Result N chromium@504251 689.09 +- 22.274 21 good chromium@504455 688.124 +- 28.1444 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=Speedometer2 speedometer2 More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8966642506978566688 For feedback, file a bug with component Speed>Bisection
,
Oct 5 2017
doesn't seem to have affected the windows runs. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 4 2017