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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4pDHvgkM


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

win-zenbook

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

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

Bisect Details
  Configuration: winx64_zen_perf_bisect
  Benchmark    : service_worker.service_worker_micro_benchmark
  Metric       : concurrent_100_response_99_percentile/concurrent_100_response_99_percentile

Revision             Result                  N
chromium@465666      126.401 +- 35.4719      21      good
chromium@465860      122.599 +- 26.5623      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979463765794134528

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5897469847666688


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Ah, I found the ref also got increased. Something might have happened on the perf bot.

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

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

Bisect Details
  Configuration: winx64_zen_perf_bisect
  Benchmark    : service_worker.service_worker_micro_benchmark
  Metric       : concurrent_100_response_99_percentile/concurrent_100_response_99_percentile

Revision             Result                  N
chromium@465666      131.72 +- 55.872        21      good
chromium@465860      126.563 +- 35.1975      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests service_worker.service_worker_micro_benchmark

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979458008823755376

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5897469847666688


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!