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

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


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

chromium-rel-win7-dual

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

=== 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_path_rendering_cases
  Metric       : frame_times/MotionMark Canvas Fill Shapes
  Change       : 6.60% | 41.2746685509 -> 43.9990291813

Revision             Result                   N
chromium@495791      41.2747 +- 0.871614      6      good
chromium@495800      41.3888 +- 2.78703       9      good
chromium@495801      41.0041 +- 0.848817      6      good
chromium@495802      43.8868 +- 1.74155       6      bad       <--
chromium@495804      44.6387 +- 0.760974      6      bad
chromium@495808      43.999 +- 2.00058        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.Canvas.Fill.Shapes smoothness.gpu_rasterization.tough_path_rendering_cases

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

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


For feedback, file a bug with component Speed>Bisection