-
-
Notifications
You must be signed in to change notification settings - Fork 557
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Key to refer to properties and cache hash code #634
Merged
Conversation
This file contains 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
This reverts commit d5e2485.
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.
I wanted to play with the idea that we use separate struct
Key
when referring to binding context or object properties. Now when we want to get variablecounter
, we build identifier which also holds calculated hash code. With this hash we can make subsequent searches faster when trying to find the correct context. Basically every object property of identifier lookup will require calculating hash code at least once. This also cleans up checking for our known commonly accessed properties where we don't want to build the dictionary unless necessary.Preliminary results
NOTE now using .NET Core App 2.2 for benchmark project for both dev branch and this work
Esprima.Benchmark.SunSpiderBenchmark
Jint.Benchmark.ArrayBenchmark
Jint.Benchmark.ArrayStressBenchmark
Jint.Benchmark.DromaeoBenchmark
Jint.Benchmark.EvaluationBenchmark
Jint.Benchmark.MinimalScriptBenchmark
Jint.Benchmark.StopwatchBenchmark
Jint.Benchmark.UncacheableExpressionsBenchmark