[refactor] - Optimize memory usage for small chunks in readInChunks
#3081
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.
Description:
This PR introduces an optimization to reduce memory usage when processing
small chunks of data in the readInChunks function. Key changes include:
a chunk is considered "small".
smaller than the threshold.
This optimization aims to improve memory efficiency for smaller chunks
while maintaining performance for larger ones. It should reduce unnecessary
memory allocation and potentially improve the speed of downstream operations
like FindDetectorMatches for smaller data chunks.
Checklist:
make test-community
)?make lint
this requires golangci-lint)?