Vespa vs Qdrant vs Turbopuffer for large-scale hybrid search (BM25 + text & image vectors) #7786
Unanswered
sumitrajrajsumit
asked this question in
Q&A
Replies: 1 comment
-
|
We can help you design such a solution with Qdrant. We have several customers with similar requirements. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone — we’re evaluating search platforms for a hybrid search use case and would appreciate insights from people who’ve used Vespa, Qdrant, or Turbopuffer in real systems.
Background
Search requirements:
What we’re trying to understand
Hybrid search capabilities
Scalability & reliability
Business logic & reranking
Performance & latency
Feature set & ecosystem
Cost considerations
Migration perspective
Open question
If you were designing a hybrid search system today for ~170M products, ~100 QPS, and sub-100 ms latency, how would you think about choosing between Vespa, Qdrant, and Turbopuffer? What factors would matter most?
Any references to documentation, benchmarks, or real-world experiences would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions