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

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


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

android-nexus5X
android-webview-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_GPU_cpu_time_per_frame/http___jsbin.com_UVIgUTa_38_quiet

Revision             Result                   N
chromium@499937      2.17761 +- 0.420611      21      good
chromium@500005      2.12456 +- 0.295482      21      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...jsbin.com.UVIgUTa.38.quiet 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/8968748886510338672


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Sunny Sachanandani
  Commit : 2eb3c8ac7ffc6840dc07f5e8312576e107eece23
  Date   : Wed Sep 06 02:01:21 2017
  Subject: cc: Flush after every tile task set completes.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_GPU_cpu_time_per_frame/http___jsbin.com_UVIgUTa_38_quiet
  Change       : 15.22% | 1.84866748433 -> 2.13007071632

Revision             Result                    N
chromium@499617      1.84867 +- 0.262369       6      good
chromium@499811      1.74674 +- 0.127735       6      good
chromium@499836      1.74365 +- 0.0937539      6      good
chromium@499842      1.80382 +- 0.150781       6      good
chromium@499844      1.85461 +- 0.101526       6      good
chromium@499845      2.15736 +- 0.115502       6      bad       <--
chromium@499848      2.16269 +- 0.200144       6      bad
chromium@499860      2.19626 +- 0.149928       6      bad
chromium@499908      2.14511 +- 0.153524       6      bad
chromium@500005      2.13007 +- 0.0839247      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...jsbin.com.UVIgUTa.38.quiet 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/8968655608800990736


For feedback, file a bug with component Speed>Bisection