Issue metadata
Sign in to add a comment
|
18%-31.9% regression in v8.runtimestats.browsing_mobile at 483678:488097 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 25 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8973091060808065168
,
Jul 25 2017
,
Jul 26 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : v8.runtimestats.browsing_mobile Metric : v8-gc-incremental-step_avg/browse_social/browse_social_facebook_infinite_scroll Revision Result N chromium@487431 0.563645 +- 0.280171 15 good chromium@487499 0.581655 +- 0.327378 18 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=browse.social.facebook.infinite.scroll v8.runtimestats.browsing_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8973091060808065168 For feedback, file a bug with component Speed>Bisection
,
Nov 21 2017
Recovered. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 25 2017