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

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


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

android-nexus5
android-nexus5X
android-nexus6
android-one
android-webview-nexus6
chromium-rel-win7-dual
chromium-rel-win7-x64-dual

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : thread_times.tough_compositor_cases
  Metric       : thread_raster_cpu_time_per_frame/thread_raster_cpu_time_per_frame

Revision             Result                    N
chromium@517168      5.08421 +- 0.0579002      5      good
chromium@517268      6.30991 +- 0.0325003      4      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 thread_times.tough_compositor_cases

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

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


For feedback, file a bug with component Speed>Bisection

This recovered.