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

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


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

chromium-rel-win7-gpu-nvidia

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

=== 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: winx64nvidia_perf_bisect
  Benchmark    : blink_perf.parser
  Metric       : query-selector-id-last/query-selector-id-last
  Change       : 21.56% | 99494.2920128 -> 78044.0439486

Revision             Result                  N
chromium@510799      99494.3 +- 790.929      6      good
chromium@510821      102828 +- 860.746       6      good
chromium@510823      101302 +- 1613.95       6      good
chromium@510824      80433.5 +- 658.596      6      bad       <--
chromium@510827      80374.2 +- 1573.76      6      bad
chromium@510832      78679.5 +- 746.307      6      bad
chromium@510843      76741.8 +- 1967.84      6      bad
chromium@510886      78044.0 +- 625.066      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.parser

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

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


For feedback, file a bug with component Speed>Bisection