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

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


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

chromium-rel-win7-dual

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

=== 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    : speedometer
  Metric       : Total/Total
  Change       : 5.03% | 6290.24175 -> 6606.39933333

Revision             Result                  N
chromium@495791      6290.24 +- 29.9436      6      good
chromium@495800      6313.36 +- 143.997      6      good
chromium@495801      6271.14 +- 40.2963      6      good
chromium@495802      6667.71 +- 101.97       6      bad       <--
chromium@495804      6638.86 +- 50.5357      6      bad
chromium@495808      6606.4 +- 61.3557       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 speedometer

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

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


For feedback, file a bug with component Speed>Bisection