Skip to content

Comments

Adding visit_percentage and rescoring to speed/accuracy section#5180

Merged
benwtrent merged 3 commits intomainfrom
adding-visit-percentage
Feb 24, 2026
Merged

Adding visit_percentage and rescoring to speed/accuracy section#5180
benwtrent merged 3 commits intomainfrom
adding-visit-percentage

Conversation

@benwtrent
Copy link
Member

closes: #5175

@benwtrent benwtrent requested a review from a team as a code owner February 17, 2026 15:25
@benwtrent benwtrent added documentation Improvements or additions to documentation v9.2.0 v9.3.0 labels Feb 17, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Feb 17, 2026

Vale Linting Results

Summary: 1 suggestion found

💡 Suggestions (1)
File Line Rule Message
solutions/search/vector/knn.md 185 Elastic.WordChoice Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 17, 2026

🔍 Preview links for changed docs

@benwtrent benwtrent requested a review from a team February 23, 2026 14:32
Copy link
Contributor

@tteofili tteofili left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, with a minor comment.


When a search targets both HNSW and DiskBBQ indices, use `visit_percentage` with `num_candidates` to tune performance and recall across both index types.

When [quantization](elasticsearch://reference/elasticsearch/mapping-reference/dense-vector.md#dense-vector-quantization) is involved, `rescore_vector` is an additional speed/accuracy tuning tool. It reranks a larger candidate set using original vectors after approximate retrieval.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perhaps we should mention that in bbq_disk, when not specified, oversampling also automatically adjusts to the quantization scheme (1-bit --> 3x, 2-bit --> 1.5x, 4-bit --> no oversampling)

Copy link
Contributor

@john-wagster john-wagster left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Copy link
Contributor

@leemthompo leemthompo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @benwtrent

@benwtrent benwtrent merged commit 454dc42 into main Feb 24, 2026
8 checks passed
@benwtrent benwtrent deleted the adding-visit-percentage branch February 24, 2026 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation v9.2.0 v9.3.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Website]: Missing section on visit_percentage and diskbbq usage

4 participants