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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : webrtc.peerconnection
  Metric       : cpu_utilization/cpu_utilization_browser

Revision             Result                  N
chromium@471245      2.02754 +- 2.07062      21      good
chromium@471282      2.1446 +- 1.18706       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 webrtc.peerconnection

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

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


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

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : webrtc.peerconnection
  Metric       : cpu_utilization/cpu_utilization_browser
  Change       : 22.37% | 1.66925297591 -> 1.32304479809

Suspected Commit Range
  14 commits in range
  https://chromium.googlesource.com/chromium/src/+log/7f86224d3bc34aa39ea8cdd21ec590b6e2954806..36cc3da5e8b2360e246342351ee0959fb9e7ffea


Revision             Result                   N
chromium@471245      1.66925 +- 1.55922       14       good
chromium@471251      1.51961 +- 1.38953       21       good
chromium@471252      ---                      ---      build failure
---                  ---                      ---      too many build failures to list
chromium@471264      ---                      ---      build failure
chromium@471265      1.27158 +- 0.915227      14       bad
chromium@471282      1.32304 +- 0.842563      14       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 webrtc.peerconnection

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

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


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