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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=01b01c6ca9c9133b0c8afafb5555f622a56b0d23571f43b73bd86a957ee650c5


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

chromium-rel-win10
chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : media_perftests
  Metric       : audio_bus_from_interleaved/int32_t

Revision             Result                   N
chromium@500308      10.4673 +- 0.665497      21      good
chromium@501429      11.2053 +- 5.24986       21      bad

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

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8968460404889660928


For feedback, file a bug with component Speed>Bisection

+crouleau@ the graphs make this look like a clear regression, but there is no ref trace and initial bisect found no regression (I'll try one more with a wider range now.)

(Probably FAQ again:)
Is lack of ref trace known/expected? Is there a known infra change around the time of the alert which might be responsible for the change? (Is this WontFix or a regression needing more 

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

(#5 is wider bisect range attempt 500263 - 501503)

Lack of ref builds is known issue. See crbug/714812. I will add this to the rotation documentation.

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : media_perftests
  Metric       : audio_bus_from_interleaved/int32_t

Revision             Result                   N
chromium@500263      10.383 +- 0.539543       21      good
chromium@501503      10.3139 +- 0.152038      21      bad

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

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8968450781893851888


For feedback, file a bug with component Speed>Bisection