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

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


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

Android Nexus5 Perf
Android Nexus6 WebView Perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/106578c0e40000

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

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/0f374eff414ec0683aafbe2aae3fd405a4fcc221
353.1 → 377.7 (+24.64)

[FCP++] Largest/Last Text Paint nits by maxlg@chromium.org
https://chromium.googlesource.com/chromium/src/+/e62b9095fe750f3dad440f98c5775c4f6ac4f165
376 → 376.9 (+0.8894)

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

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

The chart shows that the regression starts at 592127: https://pinpoint-dot-chromeperf.appspot.com/job/106578c0e40000

@oysteine could you take a look?

My CL was just about trivial refactoring on a feature behind a flag. It should be unrelated.