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

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


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

mac-10_12_laptop_low_end-perf

blink_perf.layout - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/120de51e140000

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/120de51e140000

OOP-R: GrContext::flush and glFlush at every DoRasterCHROMIUM by ccameron@chromium.org
https://chromium.googlesource.com/chromium/src/+/b2615d69395f6922a2d5b727045cfd70b73445fe
large-table-with-collapsed-borders-and-no-colspans: 1949 → 2762 (+812.4)

Disable the new tab-loading animation by pbos@chromium.org
https://chromium.googlesource.com/chromium/src/+/355b8185716292a8f145c77168ee89148ecabf31
large-table-with-collapsed-borders-and-no-colspans: 2754 → 2832 (+77.27)

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

Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

-> ccameron@, since their increase is larger. We needed to disable the new tab-loading animation so I don't think my part of this is actionable?