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

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


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

chromium-rel-win7-gpu-nvidia

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

=== 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: winx64nvidia_perf_bisect
  Benchmark    : blink_perf.layout
  Metric       : fixed-grid-lots-of-data/fixed-grid-lots-of-data
  Change       : 28.86% | 1234.6924728 -> 878.339047113

Revision             Result                  N
chromium@495801      1234.69 +- 15.7066      6      good
chromium@495802      877.697 +- 3.88247      6      bad       <--
chromium@495803      870.597 +- 31.5555      6      bad
chromium@495805      870.719 +- 8.424        6      bad
chromium@495808      878.339 +- 3.51446      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.layout

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

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


For feedback, file a bug with component Speed>Bisection