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

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


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

chromium-rel-win7-dual

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

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

Suspected Commit
  Author : Bruce Dawson
  Commit : 43b6c849b3c49f71261a71fcb40455d0e263c49d
  Date   : Mon Aug 28 01:12:50 2017
  Subject: Revert "Change default VC++ compiler from 2015 to 2017"

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : thread_times.tough_compositor_cases
  Metric       : thread_browser_cpu_time_per_frame/thread_browser_cpu_time_per_frame
  Change       : 0.69% | 16.4488967559 -> 16.5628360713

Revision             Result                    N
chromium@497681      16.4489 +- 0.138252       9      good
chromium@497683      16.4477 +- 0.0467237      6      good
chromium@497684      16.5395 +- 0.0480386      6      bad       <--
chromium@497685      16.5286 +- 0.0420948      9      bad
chromium@497688      16.542 +- 0.0261842       9      bad
chromium@497694      16.5628 +- 0.0946458      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/8969256564454640368


For feedback, file a bug with component Speed>Bisection