Issue metadata
Sign in to add a comment
|
11.1%-49% regression in blink_perf.dom at 512747:512885 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8963934209969190928
,
Nov 3 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Koji Ishii Commit : 811fe6a25ddee5065812bf50733de963e58832cb Date : Tue Oct 31 14:34:37 2017 Subject: Add CrashKey to LazyLineBreakIterator on Android Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : blink_perf.dom Metric : addRange/addRange Revision Result N chromium@512769 2398.1 +- 46.7759 6 good chromium@512815 2369.39 +- 28.7999 6 good chromium@512821 2381.95 +- 41.3132 6 good chromium@512824 2395.33 +- 16.5146 6 good chromium@512825 3572.01 +- 43.3109 6 bad <-- chromium@512826 3544.14 +- 54.6225 6 bad chromium@512827 3556.89 +- 70.927 6 bad chromium@512838 3527.22 +- 43.8504 6 bad chromium@512860 3413.06 +- 38.0899 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.dom More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8963934209969190928 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 3 2017