Add --max-bytes flag to limit bytes searched per file #3232
+172
−6
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 adds a new
--max-bytes NUMflag that tells ripgrep to only read and search the firstNUMbytes of each file or stream. This is useful when matches are expected only in a small header region (for example HTTP headers in large cache files), and can greatly reduce I/O.--max-bytes NUM(per file/stream)min(NUM, file_size)when--max-bytesis set--max-count 1for fast “find first hit in header” use casesImplements the feature requested in #3035.