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

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


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

chromium-rel-win7-dual

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : sebmarchand
  Commit : 833aa96095e1f827ffc05af8bf545a094ffa6e35
  Date   : Sat May 27 01:34:31 2017
  Subject: Changing default Windows compiler to VS2017

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : node-type/node-type
  Change       : 40.90% | 663.077995013 -> 391.882851297

Revision             Result                  N
chromium@475087      663.078 +- 8.47982      6      good
chromium@475155      665.657 +- 2.60111      6      good
chromium@475189      665.328 +- 1.53919      6      good
chromium@475206      663.61 +- 1.48117       6      good
chromium@475211      663.44 +- 1.56294       6      good
chromium@475212      311.221 +- 141.656      6      bad       <--
chromium@475213      279.782 +- 16.5575      6      bad
chromium@475215      357.985 +- 227.603      6      bad
chromium@475223      391.883 +- 228.724      6      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 blink_perf.bindings

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

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


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