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

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


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

chromium-rel-win7-dual

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

=== 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.tough_filters_cases
  Metric       : frame_times/MotionMark Focus
  Change       : 19.93% | 80.0451852634 -> 96.0015985856

Revision             Result                  N
chromium@495791      80.0452 +- 1.11242      6      good
chromium@495800      82.1524 +- 5.04579      6      good
chromium@495801      81.0679 +- 6.4805       6      good
chromium@495802      95.7806 +- 1.72335      6      bad       <--
chromium@495804      96.7103 +- 4.2898       6      bad
chromium@495808      96.0016 +- 3.48191      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.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/8970294226363181488


For feedback, file a bug with component Speed>Bisection