shared scope prototype#1197
Open
jbolda wants to merge 2 commits into
Open
Conversation
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Playing around with
@e18e/deoptto see if we can squeeze out a bit more perf. With scope being hit so often, having a shared prototype avoids some deopt.Approach
Deoptimization report
deopt: dependent allocation site transition changed (high)
deopt: unexpected name in keyed access (high)
deopt: wrong map (high)
The optimized code was specialized for objects of one shape here, but got an object with a different shape, so it had to deoptimize. Keep the objects reaching this line consistent (the same properties added in the same order) so V8 can rely on their shape.
ic: megamorphic (high)
This access saw too many different object shapes, so its inline cache went megamorphic and V8 can no longer optimize it. Keep the objects reaching this line consistent (the same properties added in the same order) so the access can stay monomorphic.
code: optimization churn (medium)
V8 re-optimized this function repeatedly without settling on a single optimized version. This churn wastes compilation work and usually points to types or object shapes that keep changing between calls. Keep the values reaching this function consistent so V8 can optimize it once and keep that code.
ic: polymorphic (medium)