[Webkit-unassigned] [Bug 139847] JavaScriptCore deeply nested "call" performance issue

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Feb 14 12:10:50 PST 2017


--- Comment #11 from Saam Barati <sbarati at apple.com> ---
(In reply to comment #7)
> (In reply to comment #6)
> > My guess is we're recursively emitting bytecode in a way that has
> > exponential blowup.
> Yeah that's totally what's happening.  That's hilarious.
> We should just have a back-off on that optimization.  Like, maintain a count
> of how deep in the "doubling" due to .call, .apply, or other jneq_ptr-based
> opts.  If more than K deep then don't do the optimization.
> Probably the most optimal way to do it would be upside down: don't do the
> optimization if there are more than K people below you in the tree who want
> to do it, so that the optimization kicks in for the leaves of that gross
> call tree.

Yeah this sounds reasonable to me.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170214/4d8dfea7/attachment.html>

More information about the webkit-unassigned mailing list