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

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


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_renderer_compositor_cpu_time_per_frame/http___nytimes.com_

Revision             Result                   N
chromium@522144      2.93267 +- 0.210925      21      good
chromium@522248      2.94376 +- 0.271938      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...nytimes.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/8960315599267775568


For feedback, file a bug with component Speed>Bisection

Looks like this is within the noise.