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

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


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

android-one

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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : smoothness.pathological_mobile_sites
  Metric       : mean_input_event_latency/http___www.theguardian.com_politics_2015_mar_09_ed-balls-tory-spending-plans-nhs-charging

Revision             Result                  N
chromium@510087      18.0256 +- 2.77261      21      good
chromium@510246      18.6709 +- 3.9783       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.theguardian.com.politics.2015.mar.09.ed.balls.tory.spending.plans.nhs.charging smoothness.pathological_mobile_sites

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

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


For feedback, file a bug with component Speed>Bisection

Very noisy and bisect couldn't repro.