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

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


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

android-nexus5

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_browser_cpu_time_per_frame/http___m.nytimes.com_

Revision             Result                    N
chromium@522320      3.94083 +- 0.0868072      21      good
chromium@522383      3.94106 +- 0.0754962      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...m.nytimes.com. 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/8960319186703354704


For feedback, file a bug with component Speed>Bisection

Looks like this is within the noise.