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

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


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

android-nexus5
android-nexus5X
android-webview-nexus6

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/1491e7b1240000

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

Remove Download.SavePageType UMA. by benjhayden@chromium.org
https://chromium.googlesource.com/chromium/src/+/7fdebead5b6eeef1079b7bcae6a460b41d03e14f
1.876e+04 → 1.849e+04 (-260.8)

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

Removing a UMA shouldn't have affected octane.

+dtu: why didn't pinpoint test commits between 564182 and 564293?

My fault. https://github.com/catapult-project/catapult/issues/4501
Re-running now.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/13bd8931240000

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

[wasm] Make stack check independent of the Isolate. by mstarzinger@chromium.org
https://chromium.googlesource.com/v8/v8/+/c96ac82c504c66be7053045ad658fe04af46d254
1.882e+04 → 1.854e+04 (-271.8)

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

2 of the 3 metrics stopped reporting data for ~2 months.  The remaining one: too noisy to be useful.