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

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


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

chromium-rel-win7-gpu-intel

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

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

Suspected Commit
  Author : Nico Weber
  Commit : 7cd2f6bd73c6a9c6200704e995b18ebb3168ead6
  Date   : Sat Aug 19 04:23:54 2017
  Subject: win: Turn off clang-by-default again for now.

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : typed-array-set-from-typed/typed-array-set-from-typed
  Change       : 10.99% | 841.426695655 -> 748.979478388

Revision             Result                  N
chromium@495793      841.427 +- 4.75667      6      good
chromium@495801      843.11 +- 3.9129        6      good
chromium@495802      748.95 +- 3.47119       6      bad       <--
chromium@495803      750.169 +- 2.08366      6      bad
chromium@495805      749.149 +- 2.38986      6      bad
chromium@495808      748.979 +- 5.00945      6      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 blink_perf.bindings

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

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


For feedback, file a bug with component Speed>Bisection