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

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


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

linux-perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/164c7555e40000

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

Avoid unnecessary call to MakeCurrent by backer@chromium.org
https://chromium.googlesource.com/chromium/src/+/ce6ad323cd9aa0c49aa7245fe942dc5b9a91e421
tasks_per_frame_total_all: 115.9 → 126.2 (+10.26)

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

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

This isn't a real regression. The reason that we have more tasks per frame is because we are rastering more pixels, resulting in less checkerboarding:

https://chromeperf.appspot.com/report?sid=3f0e58949cd3a75f75c1b7331c4c52b8df95cea015320b339f0ef15cb512b102&start_rev=604093&end_rev=608345