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

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


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

android-nexus5

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

=== 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_nexus5_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_GPU_cpu_time_per_frame/http___nytimes.com_
  Change       : 2.76% | 3.78440580751 -> 3.888868456

Revision             Result                    N
chromium@517737      3.78441 +- 0.0661912      6      good
chromium@517739      3.81884 +- 0.0628193      9      good
chromium@517740      3.8769 +- 0.074318        6      bad       <--
chromium@517741      3.88887 +- 0.077626       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=http...nytimes.com. thread_times.key_mobile_sites_smooth

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

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


For feedback, file a bug with component Speed>Bisection