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

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


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

chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : media_perftests
  Metric       : clockless_video_playback_mp4/bear_silent.mp4

Revision             Result                  N
chromium@449981      108.059 +- 7.95038      21      good
chromium@450083      108.301 +- 8.95261      21      bad

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

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

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


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

Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner.