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

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


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

chromium-rel-win7-gpu-intel

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

=== 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.shadow_dom
  Metric       : v1-small-shallow-layout/v1-small-shallow-layout
  Change       : 13.91% | 0.530666666667 -> 0.6045

Revision             Result                     N
chromium@495793      0.530667 +- 0.0156631      6      good
chromium@495801      0.537 +- 0.0166733         6      good
chromium@495802      0.6075 +- 0.0133978        6      bad       <--
chromium@495803      0.598667 +- 0.013466       6      bad
chromium@495805      0.597833 +- 0.0177435      6      bad
chromium@495808      0.6045 +- 0.0356861        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.shadow_dom

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

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


For feedback, file a bug with component Speed>Bisection