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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghIjOpQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-I7q_QoM


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

chromium-rel-win10
chromium-rel-win7-dual

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

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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : indexeddb_perf
  Metric       : Total Perf/Total Perf

Revision             Result                  N
chromium@451322      9273.58 +- 11216.8      21      good
chromium@451396      9759.36 +- 14466.2      21      bad

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

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

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


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

Ref build also regressed at got noisier at this time.

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