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

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


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

Win 7 Nvidia GPU Perf

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/10fb1782e40000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/10fb1782e40000

Reland "synthetic gesture: Allow high-frequency dispatch." by sadrul@chromium.org
https://chromium.googlesource.com/chromium/src/+/a66784e0fd71f686f1d7152902137619608c6c80
console:error:all: 314.1 → 320.3 (+6.189)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

This code only affects tests, where it dispatches input events more frequently. If there are console logs associated with input events, then it would make sense that there could be more logs. Either way, this does not affect production.