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

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


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

chromium-rel-mac12

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/149554b1840000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/15efd009840000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/149554b1840000

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

Revert "Add UKM metrics for rendering timing measurements" by cbiesinger@chromium.org
chromium @ 772b2bcdbaa8ea5c5b1f47255c6c1562016fb680

Re-enable remote QUIC alt-svc by rch@chromium.org
chromium @ 0d32636d121706cbee7cfe1d950635b3a38df43d

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

I don't think there is any possibility that this is related to the alt-svc CL as QUIC Is not used in the path of that test.

It certainly shouldn't be my revert, which was fixing perf issues I caused the day before...

Trying different point

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/1298e278440000

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

Revert "Add UKM metrics for rendering timing measurements" by cbiesinger@chromium.org
https://chromium.googlesource.com/chromium/src/+/772b2bcdbaa8ea5c5b1f47255c6c1562016fb680

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

Closing the bug since revert shouldn't be seen as a regression.
However, I didn't find that the original commit made an improvement earlier.