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

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


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

chromium-rel-win7-dual

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

=== 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: win_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_filters_cases
  Metric       : frame_times/MotionMark Focus
  Change       : 20.27% | 82.1380461342 -> 98.7847542372

Revision             Result                  N
chromium@495791      82.138 +- 7.65019       6      good
chromium@495800      82.205 +- 5.55337       6      good
chromium@495801      82.3325 +- 6.12133      6      good
chromium@495802      100.321 +- 5.25951      6      bad       <--
chromium@495804      96.1505 +- 1.93766      6      bad
chromium@495808      98.7848 +- 4.40032      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=MotionMark.Focus 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/8970294291992961232


For feedback, file a bug with component Speed>Bisection