11 ms·
HNSW seems better in the criteria that matter. I think similarity search is a commodity now; I would not invest in developing an in-house solution given the ab
by esafak 4y ago
HNSW seems better in the criteria that matter.
I think similarity search is a commodity now; I would not invest in developing an in-house solution given the abundance of good commercial solutions.
- cjbgkagh 4y agoThey’re embeddings so they’re dense. There are few things easier than dense vector similarity.
- esafak 4y agoEmbeddings for retrieval don't have to be. It is not unheard of to transform the raw embeddings to optimize them for retrieval; e.g., through binarization or hashing.
- cjbgkagh 4y agoI was more making a distinction between embeddings and bag of words which are very very sparse matrices. The embedding dimensionality will not be anywhere near as high so this level of sparsity is a minor inconvenience. Edit: also CPUs for this, yikes…
- jakearmitage 4y agoSuch as...?
- jabo 4y agoTypesense: https://typesense.org/docs/0.24.1/api/vector-search.html https://typesense.org/docs/0.24.1/api/vector-search.html
- deleted 4y ago[deleted]
- esafak 4y agoQdrant, milvus, weaviate
- kartoolOz 4y agoVespa.ai is pretty crazy too, a bit unkown we run a huge vespa cluster serving 1k+ queries with <100ms latency ...
- fzliu 4y agoWe've seen Milvus used in a variety of recommender systems running in production.
- bobvanluijt 4y agoThat depends a bit on the scale and use case specifics. But commoditized billion-scale vector search is indeed a thing. We published this for Weaviate in December last year https://weaviate.io/blog/sphere-dataset-in-weaviate https://weaviate.io/blog/sphere-dataset-in-weaviate