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

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


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

chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-nvidia
chromium-rel-win8-dual

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

=== 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.runtimestats.browsing_desktop
  Metric       : v8-gc-latency-mark-compactor_sum/browse_media/browse_media_imgur
  Change       : 140.72% | 13.2605 -> 31.9201666667

Revision             Result                  N
chromium@510799      13.2605 +- 8.04591      6      good
chromium@510821      16.1245 +- 9.50887      6      good
chromium@510823      15.5642 +- 7.98159      6      good
chromium@510824      29.3957 +- 14.6273      6      bad       <--
chromium@510827      33.1725 +- 17.1554      6      bad
chromium@510832      29.7593 +- 9.73959      6      bad
chromium@510843      33.3915 +- 10.5493      6      bad
chromium@510886      31.9202 +- 17.2485      6      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.runtimestats.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection