Issue metadata
Sign in to add a comment
|
1.7%-296.5% regression in thread_times.tough_scrolling_cases at 503949:503954 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 25 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8967447536480486272
,
Sep 25 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Brian White Commit : 7ac4e75787ae3b44a33026e4e3671410c81a273c Date : Sun Sep 24 04:33:45 2017 Subject: Validate histograms around IPC calls on Android. Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : thread_times.key_silk_cases Metric : thread_browser_cpu_time_per_frame/http___jsfiddle.net_vBQHH_11_show_ Change : 300.96% | 1.93200727421 -> 7.74653201204 Revision Result N chromium@503949 1.93201 +- 0.0245248 6 good chromium@503950 1.93007 +- 0.026652 6 good chromium@503951 7.74653 +- 0.154159 6 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=http...jsfiddle.net.vBQHH.11.show. thread_times.key_silk_cases More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8967447536480486272 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 25 2017