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

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


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

android-nexus7v2

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

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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : service_worker.service_worker_micro_benchmark
  Metric       : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile

Revision             Result                  N
chromium@489281      53.1026 +- 2.00136      21      good
chromium@489362      53.304 +- 1.38895       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 service_worker.service_worker_micro_benchmark

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

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


For feedback, file a bug with component Speed>Bisection