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

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


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

android-nexus7v2

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

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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_GPU_cpu_time_per_frame/http___cuteoverload.com

Revision             Result                   N
chromium@497006      2.9764 +- 0.170187       21      good
chromium@497059      2.96884 +- 0.231423      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...cuteoverload.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/8970006547291941264


For feedback, file a bug with component Speed>Bisection

This alert seems to be within the noise.