Document VSEARCH scaling and its flat-scan ceiling#57
Open
tchalikanti1705 wants to merge 1 commit into
Open
Conversation
The numbers from the Rohit-Dnath#13 benchmark discussion, in docs where anyone sizing a collection can see them before finding out at 100k vectors.
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
1 participant
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.
Summary
Puts the VSEARCH benchmark table from the #13 discussion into docs/benchmark.md, so the flat-scan ceiling is visible to anyone deciding whether RAMen fits their collection size.
Related Issue
Relates to #13 (left open per the discussion there — this is the docs follow-up you asked for, not the index).
Changes
Checklist
go test ./...)go fmt ./...)