This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Performance tuning/Recommendations #177
Merged
Conversation
This file contains 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
jmazanec15
reviewed
Jul 24, 2020
jmazanec15
reviewed
Jul 27, 2020
There was a problem hiding this comment.
From this it looks like all headers that do not have a space between them and the title do not show up as headers.
Still need to review more, will continue this week.
PerformanceTuning.md
Outdated
|
|
||
| ### Warm up | ||
|
|
||
| The graphs are constructed during indexing, but they are loaded into memory during the first search. The way search works in Lucene is that each segment is searched sequentially (so, for k-NN, each segment returns up to k nearest neighbors of the query point) and the results are aggregated together and ranked based on the score of each result (higher score --> better result). |
There was a problem hiding this comment.
Is there documentation for this?
jmazanec15
reviewed
Jul 28, 2020
PerformanceTuning.md
Outdated
|
|
||
| ### Warm up | ||
|
|
||
| The graphs are constructed during indexing, but they are loaded into memory during the first search. The way search works in Lucene is that each segment is searched sequentially (so, for k-NN, each segment returns up to k nearest neighbors of the query point) and the results are aggregated together and ranked based on the score of each result (higher score --> better result). |
There was a problem hiding this comment.
Interesting, makes sense thanks
jmazanec15
reviewed
Jul 28, 2020
|
|
||
| In order to avoid this latency penalty during your first queries, a user should use the warmup API on the indices they want to search. The API looks like this: | ||
|
|
||
| GET /_opendistro/_knn/warmup/index1,index2,index3?pretty |
PerformanceTuning.md
Outdated
|
|
||
| The following steps could help improve indexing performance especially when you plan to index large number of vectors at once. | ||
|
|
||
| 1 Disable refresh interval (Default = 1 sec) |
There was a problem hiding this comment.
Minor: add "." after numbering
jmazanec15
approved these changes
Jul 28, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Issue #, if available:
#64
Description of changes:
Adds Performance tuning/Recommendations to improve indexing/search performance.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.