Improve the performance of SwiftParseUtils.getLines(...)#301
Merged
zubri merged 1 commit intoprowide:mainfrom Apr 1, 2026
Merged
Improve the performance of SwiftParseUtils.getLines(...)#301zubri merged 1 commit intoprowide:mainfrom
zubri merged 1 commit intoprowide:mainfrom
Conversation
Signed-off-by: Seppe Volkaerts <seppevolkaerts@hotmail.com>
zubri
approved these changes
Apr 1, 2026
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
3 participants
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.
Reimplements
SwiftParseUtils.getLines(...)without usingStringReaderandBufferedReader, this function is currently a hotspot in our high performance scenarios and reimplementing like this eliminates the hotspot. (A newBufferedReadereach time is quite heavy for a lot of fields in an input file.)