Issue metadata
Sign in to add a comment
|
137% regression in v8.browsing_mobile at 492518:492573 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8971563484233385952
,
Aug 11 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : v8.browsing_mobile Metric : v8-gc-scavenger_avg/browse_media/browse_media_imgur Revision Result N chromium@492517 18.7908 +- 15.8029 21 good chromium@492573 18.2284 +- 16.3961 21 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 --story-filter=browse.media.imgur v8.browsing_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8971563484233385952 For feedback, file a bug with component Speed>Bisection
,
Aug 11 2017
No repro, regression recovered. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 11 2017