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

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


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

android-nexus6

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

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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_browser_cpu_time_per_frame/http___www.nyc.gov

Revision             Result                   N
chromium@516557      2.6583 +- 0.290065       21      good
chromium@516592      2.69552 +- 0.261113      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...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/8962314773469039680


For feedback, file a bug with component Speed>Bisection

Very noisy. Not convinced the regression is real.