Culprit that caused the regression: #7445

After speaking with @stevegolton on the Perfetto team, the hypothesis is that this was caused by plugin initialization added in google/perfetto@24a0d91 (first included in v36.0).

Immediate action:

• Roll back our perfetto build to avoid the regression.
  • EDIT: I was able to use v34.0 with a local patch to include https://android-review.git.corp.google.com/c/platform/external/perfetto/+/3015413
    • see Restore old version of Perfetto to fix performance regression #7480

Longer term action:

• work with the Perfetto team to see if we can avoid expensive initialization on each trace load.