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

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


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

Android Nexus5 Perf
Android Nexus6 WebView Perf
linux-perf
mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/17b1f971e40000

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

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@chromium.org
https://chromium.googlesource.com/chromium/src/+/3bb24369bef996b43b2d2711f0033ba472f779ea
Registry::RegisterBlob: 71.61 → 79.67 (+8.058)

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

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

Seems to be missing some thread names too (see browser process):

before: https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/blob_perf_files_html_2018-11-20_02-48-04_19030.html
after:  https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/blob_perf_files_html_2018-11-20_02-50-55_17091.html

from: https://pinpoint-dot-chromeperf.appspot.com/job/1231fb38140000

As well as some missing threads (TaskSchedulerForegroundWorker, e.g. in the renderer). There's quite clearly a period in the second trace where another worker thread was active but is missing from the trace.

before: https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/blob_perf_ipc_html_2018-11-20_02-48-22_8074.html
after:  https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/blob_perf_ipc_html_2018-11-20_02-51-16_40851.html

(from same pinpoint job).

Looks like http://crrev.com/612360 recovered this one as well (where there's data).