perf: chunker json parsing 75% faster using simdjson-go #7315
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
karlmcguire
added
area/performance
|
Putting this PR on the backburner. Performance benefit isn't worth the added complexity. |
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.
This fully replaces the current JSON parser. I recommend that we use the
simdjson.SupportedCPU()function to determine which JSON parser to use at runtime.The current performance increases are mostly from simdjson-go, I'm sure there is more room to optimize.
NOTE: This is pertinent on simdjson-go merging this pull request to fix number parsing issues.
This change is