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

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


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

linux-release

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/11e66e89440000

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

Enable root layer scrolling. by skobes@chromium.org
https://chromium.googlesource.com/chromium/src/+/96f85b68747a679ea1ac4cd05d6743ae5f7142b7

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

szager do you think there's anything actionable here?

I think it's worth seeing if we can reproduce the result locally by running with RLS enabled/disabled.  It's on desktop, so should be easier than mobile.

hi, friendly reminder ping from today's perf sheriff.

Is this regression recovered now?

This did not recover. (If you extend out the graphs, you'll see the reference build regressing too--that's when we upgraded the ref build to latest stable)

Ping! This bug has been flagged as stale by Chrome Speed Metrics bug triage, and it has an owner. Any update on this issue?