Issue metadata
Sign in to add a comment
|
3%-7.5% regression in speedometer at 508926:508936 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8965605387059933312
,
Oct 16 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_one_perf_bisect Benchmark : speedometer Metric : VanillaJS-TodoMVC/VanillaJS-TodoMVC Revision Result N chromium@508928 2732.84 +- 443.545 18 good chromium@508936 2726.12 +- 303.932 15 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --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/8965605387059933312 For feedback, file a bug with component Speed>Bisection
,
Oct 16 2017
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 16 2017