Implement zero-copy tokenization for identifiers, strings, and comments #2136
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 PR implements zero-copy tokenization by using borrowed strings (
&str) instead of owned strings (String) for identifiers, string literals, and comments. This eliminates unnecessary string allocations during the tokenizationprocess.
Changes
Tokenvariants to store&'a strinstead ofStringfor:Wordtokens (identifiers like table/column names)SingleQuotedStringliteralsWhitespaceto_uppercase()allocationtokenize_benchcriterion benchmark for performance measurementPerformance Impact
Benchmark results using a complex 27KB SQL query with CTEs, joins, window functions, and extensive comments:
tokenization/tokenize_complex_sql
time: [254.68 µs 254.81 µs 254.97 µs]
change: [−60.885% −60.682% −60.482%] (p = 0.00 < 0.05)
Performance has improved.