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

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


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

chromium-rel-win7-x64-dual

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

=== 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: win_x64_perf_bisect
  Benchmark    : blink_perf.parser
  Metric       : query-selector-deep/query-selector-deep
  Change       : 49.16% | 11352.962532 -> 5771.53112779

Revision             Result                  N
chromium@495800      11353.0 +- 1526.96      6      good
chromium@495801      11341.3 +- 888.437      6      good
chromium@495802      5692.77 +- 57.5435      6      bad       <--
chromium@495804      5659.86 +- 178.204      6      bad
chromium@495808      5771.53 +- 121.529      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.parser

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

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


For feedback, file a bug with component Speed>Bisection