Dynamic buffer size #75
Merged
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 dynamic sizing of the buffer used by
tree-sitter, to fix #74 . The default 32 KB buffer size is maintained, but any files over that size will be parsed with a dynamic buffer size matching the file size + 32 bytes of padding instead.I suggest that a warning is logged for files where the size starts to noticeably affect performance. It's currently set to 2 MB but I'm of course open to suggestions to change it. Logging for every file is over 32 kb might get noisy in some codebases.
Here are some performance metrics captured on my Macbook Pro M1: