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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2JjvtgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmOWShQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmIrY4ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2PK66ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmJ--8AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmInOlwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmMiEjggM


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

chromium-rel-win7-dual
chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : media_perftests
  Metric       : vector_math_fmul/optimized_unaligned

Revision             Result                  N
chromium@449769      787.109 +- 10.4348      21      good
chromium@449839      788.157 +- 11.3211      21      bad

To Run This Test
  .\src\out\Release\media_perftests.exe --single-process-tests

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

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


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

The graph shows that this has recovered.