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

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


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

android-nexus5

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14bf562ec40000

📍 Found significant differences after each of 3 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/14bf562ec40000

Remove PORTALLOCATOR_ENABLE_SHARED_UFRAG by steveanton@webrtc.org
https://webrtc.googlesource.com/src/+/c4384ea13851a006f6637ae55f612645f5dad474

Roll src/third_party/webrtc/ 3acffc3b1..365381fdf (3 commits) by webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/cca5fb486974e3819b06c12e490fa4fc94e7319a

Roll AFDO from 67.0.3396.0_rc-r1 to 68.0.3397.0_rc-r1 by afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/64b21547275ff8bb7f28d77d109186ff5727e146

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

gbiv: I do see a slight jump at the AFDO roll to 68.0.3397.0_rc-r1.

cblume: is a small regression just on N5 worth investigating further?

My heart wants to say "investigate all the performance things!"

But the reality is I don't have time for it all and need to pick the lowest hanging fruit. This regression is definitely not the lowest hanging fruit. :) I'm happy to let it go.