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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-LLwsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-Ob0vAsM


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

chromium-rel-win7-gpu-intel
chromium-rel-win7-x64-dual

...and on chromium-rel-mac10.

Minimum range for regression is only two changes: 386659 or 386660.  The main suspect is:

commit	0a263edeb740bb85eebfe9df27ba5870db1801b6	
author	v8-autoroll <v8-autoroll@chromium.org>	Tue Apr 12 12:34:26 2016
committer	Commit bot <commit-bot@chromium.org>	Tue Apr 12 12:35:54 2016
Update V8 to version 5.2.10.1 (cherry-pick).

Assigning to OWNER for further triage...

tkent@, could you advise? When the suspect is v8-autoroll, who should be the owner?

Assign hablich@ for triage.

Suspecting https://chromium.googlesource.com/v8/v8/+/4dfc6254fb91b0d058f4c10bd88c897833826f3a (ship try/catch for TF).

Jaro & Michael WDYT?

Just for completeness: We regress because of Turbofan compilation time - Turbofan is orders of magnitude slower than fullcode. This CL just uses Turbofan for more code.

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Perf sheriff ping

Looks like this was a tradeoff that we accepted -- jarin@, is there anything else that we want to do here, or should this bug be closed?

Yes, we took the trade-off. Closing.