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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg9u3f-QgM


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

android-webview-nexus5X

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

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

Suspected Commit
  Author : thakis
  Commit : f823f843f06636feb082521d76c282a16fe2d577
  Date   : Sat Jun 10 17:33:46 2017
  Subject: android: switch from gcc to clang.

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_IO_cpu_time_per_frame/thread_IO_cpu_time_per_frame
  Change       : 2.35% | 3.00276099962 -> 3.07320933244

Revision             Result                    N
chromium@478516      3.00276 +- 0.0600864      6      good
chromium@478517      3.07321 +- 0.0758905      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 thread_times.simple_mobile_sites

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976608514687874736

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5976783188393984


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!