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

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


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

Android Nexus5 Perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/105ffa2be40000

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

EnableGpuRasterizationViewportRestriction bot config by ericrk@chromium.org
https://chromium.googlesource.com/chromium/src/+/924edd7aee62613bf0d3f51b4c4d00e63f5c104e
mean_pixels_approximated: 0.009367 → 0 (-0.009367)

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

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

We expect GPU Rasterization to have this kind of impact, as tile rasterization should be significantly sped up. We had delayed turning it on on desktop sites due to an abundance of caution, but things like this are why we we should try to push the feature out.