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

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


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

chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-nvidia

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

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

Suspected Commit
  Author : Hans Wennborg
  Commit : 22525134c75ca2a005997a717f6887a23af86210
  Date   : Mon Oct 23 17:10:25 2017
  Subject: win: Re-enable Clang by default

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-latency-mark-compactor_sum/browse_media/browse_media_imgur
  Change       : 134.80% | 12.3161111111 -> 28.9176666667

Revision             Result                  N
chromium@510799      12.3161 +- 6.08936      9      good
chromium@510821      11.9695 +- 8.4601       6      good
chromium@510823      15.016 +- 6.15586       6      good
chromium@510824      32.5192 +- 18.3647      6      bad       <--
chromium@510827      27.8422 +- 4.74944      6      bad
chromium@510832      29.5472 +- 7.49839      6      bad
chromium@510843      28.9777 +- 12.0181      6      bad
chromium@510886      28.9177 +- 26.0342      9      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 --story-filter=browse.media.imgur v8.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection