Issue metadata
Sign in to add a comment
|
15.7%-39.7% regression in v8.runtimestats.browsing_mobile at 515037:515084 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8962310312930874912
,
Nov 21 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_sum/browse_tech/browse_tech_discourse_infinite_scroll Revision Result N chromium@515036 43.0384 +- 36.8449 21 good chromium@515084 41.4159 +- 26.9007 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=browse.tech.discourse.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/8962310312930874912 For feedback, file a bug with component Speed>Bisection
,
Nov 22 2017
Closing as not reproducible. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 21 2017