Issue metadata
Sign in to add a comment
|
9.9%-21.5% regression in blink_perf.css at 503949:503952 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 25 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8967445298228567040
,
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 : blink_perf.owp_storage Metric : IDBFactory::open/IDBFactory::open Change : 18.37% | 4.38625833333 -> 5.19195833332 Revision Result N chromium@503949 4.38626 +- 0.131819 6 good chromium@503950 4.35518 +- 0.106707 6 good chromium@503951 5.19196 +- 0.1349 6 bad <-- Please refer to the following doc on diagnosing blink_perf regressions: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md 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 blink_perf.owp_storage More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8967445298228567040 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