Repository navigation
feat: Store BM25 postings as numpy arrays - #284
Merged
Merged
Conversation
…, clearer load checks
Codecov Report✅ All modified and coverable lines are covered by tests.
🚀 New features to boost your workflow:
|
 |
![greptile-apps[bot]](/web-api/iframe-proxy?url=https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
…able or invalid offsets on load
stephantul
approved these changes
Oct 6, 2026
stephantul
left a comment
stephantul
left a comment
Contributor
There was a problem hiding this comment.
Small comments, looks great
…t renumber pairs, NUL check, consistency check function
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
2 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.
Loading a cached index rebuilt the BM25 inverted index in Python on every load. BM25 postings are now stored as term-sorted numpy arrays, and loading them is a plain
np.loadwhich is much faster on large caches while also reducing peak memory and making the index slightly smaller. This mainly matters for the CLI since there every query is a warm query. The benchmark scores are the exact same.Results on a repo with 27k files and 443k chunks: