fix: inconsistent FLAT/HNSW algorithm recommendations#409
Merged
Conversation
nkanu17
changed the title
rbs333
approved these changes
Oct 22, 2025
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.
Updated algorithm recommendations in docs/api/schema.rst to provide consistent, performance-based guidance:
FLAT Algorithm:
• Before: Mixed recommendations (<10K in some places, <100K in others)
• After: Consistent <100K vectors recommendation across all sections
HNSW Algorithm:
• Before: 10K-1M+ vectors (creating a gap between FLAT and HNSW)
• After: 100K-1M+ vectors (providing clear transition point)