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

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


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

chromium-rel-win7-dual

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Bruce Dawson
  Commit : eaccacb6302f7b0ea235fd7d1ff3aa7eaf8b20ef
  Date   : Mon Sep 18 06:35:37 2017
  Subject: Revert "Make VS 2017 the default compiler on Windows"

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : thread_times.tough_compositor_cases
  Metric       : thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame
  Change       : 0.98% | 18.2614500589 -> 18.439931854

Revision             Result                    N
chromium@502533      18.2615 +- 0.150094       6      good
chromium@502534      18.3021 +- 0.199387       9      good
chromium@502535      18.4814 +- 0.0929117      6      bad       <--
chromium@502536      18.4254 +- 0.121543       6      bad
chromium@502538      18.457 +- 0.0983824       6      bad
chromium@502542      18.4301 +- 0.0860856      6      bad
chromium@502550      18.4399 +- 0.117408       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 thread_times.tough_compositor_cases

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

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


For feedback, file a bug with component Speed>Bisection