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

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


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

chromium-rel-win7-gpu-intel

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

=== 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.svg
  Metric       : WorldIso/WorldIso
  Change       : 14.21% | 43.113 -> 49.2375

Revision             Result                   N
chromium@495793      43.113 +- 0.342          6      good
chromium@495801      43.7863 +- 1.06448       6      good
chromium@495802      49.5195 +- 0.189993      6      bad       <--
chromium@495803      52.4367 +- 7.18877       6      bad
chromium@495805      49.3557 +- 0.373959      6      bad
chromium@495808      49.2375 +- 0.397783      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.svg

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

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


For feedback, file a bug with component Speed>Bisection