Issue metadata
Sign in to add a comment
|
1.1%-54.4% regression in v8.mobile_infinite_scroll_tbmv2 at 482942:483040 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974917258244597664
,
Jul 6 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : v8.mobile_infinite_scroll_tbmv2 Metric : v8-gc-incremental-step_avg/facebook Revision Result N chromium@482949 0.543923 +- 0.103827 21 good chromium@483006 0.547009 +- 0.114292 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=facebook v8.mobile_infinite_scroll_tbmv2 More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8974917258244597664 For feedback, file a bug with component Speed>Bisection
,
Aug 18 2017
These were either really small or returned to normal levels. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by rmcilroy@chromium.org
, Jul 5 2017