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

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


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

chromium-rel-win7-dual

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

=== 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: win_perf_bisect
  Benchmark    : blink_perf.events
  Metric       : EventsDispatching/EventsDispatching
  Change       : 22.44% | 1274.49451074 -> 988.521403299

Revision             Result                  N
chromium@510820      1274.49 +- 47.8992      6      good
chromium@510823      1269.27 +- 29.9509      6      good
chromium@510824      974.224 +- 17.4271      6      bad       <--
chromium@510825      987.247 +- 4.26938      6      bad
chromium@510826      978.181 +- 4.80219      6      bad
chromium@510832      974.14 +- 12.3678       6      bad
chromium@510843      984.757 +- 17.9017      6      bad
chromium@510865      987.226 +- 4.81462      6      bad
chromium@510909      988.521 +- 4.2578       6      bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.events

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

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


For feedback, file a bug with component Speed>Bisection