Issue metadata
Sign in to add a comment
|
3.1%-3.3% regression in speedometer at 504142:504279 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 28 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8967203152188541680
,
Sep 28 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: win_x64_perf_bisect Benchmark : speedometer Metric : AngularJS-TodoMVC/AngularJS-TodoMVC Revision Result N chromium@504141 537.427 +- 26.4394 21 good chromium@504249 537.227 +- 25.3821 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 speedometer More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8967203152188541680 For feedback, file a bug with component Speed>Bisection
,
Sep 29 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 28 2017