-
Notifications
You must be signed in to change notification settings - Fork 1.1k
perf: improve field indexing in JSON StructArrayDecoder (1.7x speed up) #9086
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
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
1ad724f
feat: add benchmark for JSON reader performance and improve field ind…
Weijun-H f25902d
refactor: streamline StructArrayDecoder initialization by combining d…
Weijun-H 47bd73b
chore
Weijun-H 1195aa2
chore
Weijun-H 04bea37
refactor: replace child_pos with field_tape_positions in StructArrayD…
Weijun-H ad44ec2
refactor: replace Vec<u32> with FieldTapePositions in StructArrayDeco…
Weijun-H File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
qq: Do lifetimes coincide so that we could return
Option<HashMap<&str, usize>>instead?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the lifetimes do coincide. we can use
HashMap<&'a str, usize>by takingfields: &'a Fieldsas a parameter, which avoids the self-referential struct problem. However, this would require threading the lifetime parameter<'a>through the entire decoder system across many files. Since the lookup performance is identical, I don’t think it’s worth the added complexity.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe it would be a good follow on PR