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

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


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

chromium-rel-win10

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

=== 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: winx64_10_perf_bisect
  Benchmark    : blink_perf.parser
  Metric       : query-selector-deep/query-selector-deep
  Change       : 41.47% | 13026.3713509 -> 7624.04250974

Revision             Result                  N
chromium@495784      13026.4 +- 335.348      6      good
chromium@495796      13599.5 +- 364.264      6      good
chromium@495799      12845.2 +- 227.955      6      good
chromium@495801      13032.7 +- 385.211      6      good
chromium@495802      7387.26 +- 85.6326      6      bad       <--
chromium@495808      7624.04 +- 125.186      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/8970448877374714864


For feedback, file a bug with component Speed>Bisection