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

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


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

chromium-rel-win7-gpu-intel

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

=== 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.paint
  Metric       : paint-offset-changes/paint-offset-changes
  Change       : 17.12% | 164.585083333 -> 192.762416667

Revision             Result                  N
chromium@495793      164.585 +- 1.33094      6      good
chromium@495801      166.105 +- 2.03993      6      good
chromium@495802      192.315 +- 2.09262      6      bad       <--
chromium@495803      193.76 +- 0.57933       6      bad
chromium@495805      195.641 +- 1.2166       6      bad
chromium@495808      192.762 +- 1.10504      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.paint

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

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


For feedback, file a bug with component Speed>Bisection