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

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


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

chromium-rel-win7-gpu-intel

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

=== 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.layout
  Metric       : floats_100_100/floats_100_100
  Change       : 9.25% | 80.7073333333 -> 88.1741666667

Revision             Result                   N
chromium@495793      80.7073 +- 0.515957      6      good
chromium@495801      80.133 +- 0.484628       6      good
chromium@495802      87.641 +- 1.11779        6      bad       <--
chromium@495803      88.3602 +- 0.643909      6      bad
chromium@495805      87.8472 +- 0.489574      6      bad
chromium@495808      88.1742 +- 0.311318      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/8970443538016387472


For feedback, file a bug with component Speed>Bisection