Optimize field parsing #2102
Merged
Optimize field parsing #2102
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
kyri-petrou
commented
Jan 30, 2024
| index | ||
| ) | ||
| P(Index ~ name ~ aliasOrName.? ~ arguments.? ~ directives.? ~ selectionSet.?).map { | ||
| case (index, alias, Some(name), args, dirs, sels) => |
There was a problem hiding this comment.
This is the main optimization. If the 3rd parser succeeded (indicated by Some(_)), then it means we have an alias. This is much faster because the 3rd parser (aliasOrName) contains the : assertion at the start of the string rather than the end
ghostdogpr
approved these changes
Jan 30, 2024
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.
Improves performance ~15-20% of the parser. The main optimization comes from avoiding parsing the field name twice in cases that it's not aliased (which is almost always)