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

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


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

chromium-rel-win7-x64-dual

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

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

Suspected Commit
  Author : Hans Wennborg
  Commit : 22525134c75ca2a005997a717f6887a23af86210
  Date   : Mon Oct 23 17:10:25 2017
  Subject: win: Re-enable Clang by default

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : typed-array-construct-from-array/typed-array-construct-from-array
  Change       : 14.21% | 580.938285692 -> 498.412187146

Revision             Result                   N
chromium@510776      580.938 +- 1.22881       6      good
chromium@510814      580.348 +- 2.54476       6      good
chromium@510819      580.252 +- 2.99553       6      good
chromium@510822      580.523 +- 4.35554       6      good
chromium@510823      580.377 +- 2.86963       6      good
chromium@510824      497.193 +- 2.09514       6      bad       <--
chromium@510833      497.808 +- 0.847799      6      bad
chromium@510851      498.412 +- 5.92131       6      bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

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/8964677012728447392


For feedback, file a bug with component Speed>Bisection