Issue metadata
Sign in to add a comment
|
4.1%-5.1% regression in speedometer2 at 520268:520404 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 4 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8961151169301166960
,
Dec 4 2017
=== BISECT JOB RESULTS === Perf regression found but unable to narrow commit range Build failures prevented the bisect from narrowing the range further. Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : speedometer2 Metric : VanillaJS-TodoMVC/Speedometer2 Change : 1.04% | 1173.54968254 -> 1185.75150794 Suspected Commit Range 2 commits in range https://chromium.googlesource.com/chromium/src/+log/fb937c71be344b6ba74425a30f3fb1209a06c9fb..bb2075717cee645d820129b4e5ef7872dfd22661 Revision Result N chromium@520267 1173.55 +- 56.622 21 good chromium@520307 1166.3 +- 33.5904 6 good chromium@520327 1175.58 +- 44.5203 14 good chromium@520329 1184.71 +- 51.4282 21 good chromium@520330 --- --- build failure chromium@520331 1197.84 +- 52.959 14 bad chromium@520337 1184.77 +- 42.3058 14 bad chromium@520347 1185.75 +- 53.4458 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --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/8961151169301166960 For feedback, file a bug with component Speed>Bisection
,
Dec 5 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Dec 4 2017