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

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


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

Win 7 Nvidia GPU Perf

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/115cff18e40000

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

Enable automatic flush for canvas context by sunnyps@chromium.org
https://chromium.googlesource.com/chromium/src/+/f3fd321621a946f69068fa5d50dc0c9c505a6bab
65.3 → 147.5 (+82.24)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

Regression in tasks_per_frame in heavy canvas pages is expected since this CL enables more flushes to improve canvas throughput to fix an M69 stable release blocker.  This brings us back to below before the transfer buffer changes (r574816) had the side effect of flushing canvas less often.