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

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


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

chromium-rel-win10

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

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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : speedometer
  Metric       : React-TodoMVC/React-TodoMVC

Revision             Result                  N
chromium@454662      778.616 +- 47.0512      21      good
chromium@454740      782.024 +- 57.1602      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 speedometer

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

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


| 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!