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

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


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

chromium-rel-win7-dual

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

=== 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    : startup.warm.blank_page
  Metric       : open_tabs_time/open_tabs_time
  Change       : 21.40% | 18.5 -> 22.4583333333

Revision             Result                  N
chromium@495791      18.5 +- 2.76134         6      good
chromium@495800      18.375 +- 0.847791      6      good
chromium@495801      18.125 +- 1.44698       6      good
chromium@495802      23.5 +- 0.612372        6      bad       <--
chromium@495804      23.1667 +- 2.59005      6      bad
chromium@495808      22.4583 +- 1.85124      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=5 --also-run-disabled-tests startup.warm.blank_page

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

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


For feedback, file a bug with component Speed>Bisection