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

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


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

chromium-rel-win7-dual

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

=== 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: win_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_filters_cases
  Metric       : frame_times/IE PirateMark
  Change       : 10.62% | 23.8600748939 -> 21.3268067261

Revision             Result                   N
chromium@510820      23.8601 +- 0.671163      6      good
chromium@510823      23.5075 +- 0.548318      6      good
chromium@510824      20.632 +- 0.49998        6      bad       <--
chromium@510825      20.7681 +- 0.614058      6      bad
chromium@510826      20.6992 +- 0.538736      6      bad
chromium@510832      20.5877 +- 0.615348      6      bad
chromium@510843      20.6139 +- 0.582304      6      bad
chromium@510865      20.962 +- 0.76351        6      bad
chromium@510909      21.3268 +- 0.488906      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=IE.PirateMark smoothness.gpu_rasterization.tough_filters_cases

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

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


For feedback, file a bug with component Speed>Bisection