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

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


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

android-webview-nexus6

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

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_GPU_cpu_time_per_frame/http___www.nyc.gov

Revision             Result                    N
chromium@496954      0.971487 +- 0.167337      21      good
chromium@497122      0.961171 +- 0.148124      20      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 --story-filter=http...www.nyc.gov thread_times.simple_mobile_sites

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

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


For feedback, file a bug with component Speed>Bisection

Not sure what happened, but these all came right back down after a few runs.