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

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


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

chromium-rel-win8-dual

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12806bf6440000

📍 Found significant differences after each of 4 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/12806bf6440000

[builtins] Enable embedded builtins and add testing variants by jgruber@chromium.org
https://chromium.googlesource.com/v8/v8/+/abcc28ced071faee637d5fd59d06cfdf80d8ea3f

[in-place weak refs] Add in-place weak references & migrate one WeakCell to it. by marja@chromium.org
https://chromium.googlesource.com/v8/v8/+/07c1e641d9864cb2de9692cf69bccca4b49a6f6a

Revert "[in-place weak refs] Add in-place weak references & migrate one WeakCell to it." by sigurds@chromium.org
https://chromium.googlesource.com/v8/v8/+/73d6037c2051816fe926ae127aa52e863a800189

[es2015] Refactor the JSArrayIterator. by bmeurer@chromium.org
https://chromium.googlesource.com/v8/v8/+/06ee127b75726f9ee541aab10f6aecfe4d96675a

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

Ops, wrong bug. The RegExp regression might be related to the builtins refactoring?

Yes, there's a known 5-15% regression that comes with embedded builtins. My current priority is to fix that (and otherwise revert to non-embedded builds for the next roll).