Cache property enumeration in JSON.stringify like we do for Object.assign#4907
Merged
chakrabot merged 2 commits intoApr 2, 2018
Merged
Conversation
MSLaguana
approved these changes
Mar 29, 2018
MikeHolman
approved these changes
Mar 29, 2018
Contributor
Author
|
@dotnet-bot |
Contributor
Author
|
@dotnet-bot test OSX static_osx_osx_debug please |
chakrabot
pushed a commit
that referenced
this pull request
Apr 2, 2018
…fy like we do for Object.assign Merge pull request #4907 from sethbrenith:user/sethb/stringify-cache-iter JSON payloads tend to be relatively repetitive, so we can save a lot on large serializations by reusing object property iteration. On a microbenchmark that serializes and parses a repetitive piece of data that I found in Speedometer, I see a 35% improvement.
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.
JSON payloads tend to be relatively repetitive, so we can save a lot on large serializations by reusing object property iteration. On a microbenchmark that serializes and parses a repetitive piece of data that I found in Speedometer, I see a 35% improvement.