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

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


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

android-webview-nexus6

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

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

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

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

Disable embedded builtins by jgruber@chromium.org
https://chromium.googlesource.com/v8/v8/+/e0c3f6d6ca005185e537fb85bbe841fe5dae5240
7.204 → 15.76 (+8.561)

[oilpan] Cleanup tracing scopes by mlippautz@chromium.org
https://chromium.googlesource.com/chromium/src/+/c6ff060cc760c7cb8a44be7314ce5e96757213c6
15.37 → No values

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

Interesting, seems like embedded builtins improve v8-gc-latency-mark-compactor times. Since this bisects to my revert and we're planning to reland, closing as WontFix.