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

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


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

mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/10fab8b9640000

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

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/df5976ffb0d467838a97f6fe39a208208615b064
83.84 → 196.7 (+112.9)

Mac OOP-D: Enable OOP-D for Mac Waterfall by fsamuel@chromium.org
https://chromium.googlesource.com/chromium/src/+/00ec720decf72b496b1b5bd5bd16bcc85d04ec03
205.7 → 235 (+29.28)

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

Perfetto CL reverted in https://chromium-review.googlesource.com/c/chromium/src/+/1194837

 Issue 879166  has been merged into this issue.

There are 888 individual regressions here. Most of these regressions are big (the "average" regression is ~50%).

I'm very inclined to WontFix this, but I'll put a bit more time into seeing what exactly is being measured here.

The "Show (Hide) all improvements" button on top right can be used to see if these regressions have corresponding improvements.

cc-ing the test owners in case they have any suggestions.