All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=737663

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7vbSnggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrpP2vwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrpP2vwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrpvh1AgM


Bot(s) for this bug's original alert(s):

android-webview-nexus6

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975519308781107168

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Takayoshi Kochi
  Commit : fa75e2abb23205caa6d7f61edc89e672e83f6089
  Date   : Wed Jun 28 08:22:13 2017
  Subject: Revert of Relanding [Android] Adding Smart GO/NEXT feature in Chrome (patchset #4 id:80001 of https://codereview.chromium.org/2948593002/ )

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_GPU_cpu_time_per_frame/thread_GPU_cpu_time_per_frame
  Change       : 34.42% | 0.626745350275 -> 0.842472444316

Revision             Result                     N
chromium@482916      0.626745 +- 0.0244793      8      good
chromium@482917      0.624312 +- 0.011269       6      good
chromium@482918      0.851304 +- 0.047723       5      bad       <--
chromium@482919      0.853793 +- 0.02044        5      bad
chromium@482921      0.849616 +- 0.0204344      6      bad
chromium@482926      0.842472 +- 0.0171384      5      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 thread_times.simple_mobile_sites

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8975519308781107168


For feedback, file a bug with component Speed>Bisection