This repository was archived by the owner on Jan 2, 2025. It is now read-only.
Qdrant performance tuning #757
Merged
Conversation
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
ggordonhall
reviewed
Jul 17, 2023
rsdy
force-pushed
the
qdrant-perf-tuning
branch
13 times, most recently
from
2b3a841 to
870afa4
Compare
Co-authored-by: Gabriel Gordon-Hall <ggordonhall@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In Kube it seems like we need a bit more tolerance, as qdrant isn't as fast to consolidate writes as we'd like. Add random backoff to retries, wait for write confirmation during indexing, tune the qdrant WAL & keep more things in memory to get a faster resolution.