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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=24ed454da53cc3519ce4f5d1346c7027d938a450d32090e68814e45a99e25b15


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

android-one

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

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

Suspected Commit
  Author : Robert Sesek
  Commit : 6f117f26d776f0ba5657451d89800f556a30c3f3
  Date   : Mon Nov 20 00:56:36 2017
  Subject: Introduce the new CrashKeyString API.

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_GPU_cpu_time_per_frame/silk_finance.html
  Change       : 6.01% | 3.70168529754 -> 3.92428713008

Revision             Result                    N
chromium@517734      3.70169 +- 0.0852778      6      good
chromium@517737      3.67169 +- 0.0630394      6      good
chromium@517739      3.6524 +- 0.039436        6      good
chromium@517740      3.92723 +- 0.0398562      6      bad       <--
chromium@517746      3.92429 +- 0.0695121      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=silk.finance.html 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/8962042951958227120


For feedback, file a bug with component Speed>Bisection