4 ms·
I'm curious why you say 'more common'. When we did some adoption analysis, we found elastic vector indexes to have much more traction than others (excluding say
by lmeyerov 4y ago
I'm curious why you say 'more common'. When we did some adoption analysis, we found elastic vector indexes to have much more traction than others (excluding say faiss), even if it's a small % of elastic's advertising. How did you come to finding pinecone is the more common method?
- gk1 4y agoI meant OpenAI + Vector Database as more common than OpenAI Search API. And then Pinecone as an example of a vector database.
- lmeyerov 4y agoAh yes, thanks! Yeah we saw faiss + es leaders for serving embeddings / vector search, and pinecone / weaviate / I think milvus as next tier, so was curious if we could improve the analysis :)
- gk1 4y agoIs the analysis public? I'm curious how you determined the popularity of a product like Pinecone, since we don't have a public metric like GitHub stars.
- lmeyerov 4y agoLoosely measure search, CVs, and job ads: https://gradientflow.com/the-vector-database-index/ https://gradientflow.com/the-vector-database-index/ This kind of analysis is rarely precise, but is useful for rougher tasks like tiering My personal question is if vector indexes are/will be a good-enough general DB feature / compute lib for most users & use cases. A lucrative niche market can still happen as VC dollars disappear, similar to graph DBs, so not a knock, just important for folks deciding how to build things.
- andre-z 4y agoFAISS is depreciating since it is just a library that does not scale and lacks a lot of vector db functionalities like filtering. ES is often used just by default because Devs have experience with but the performance is very low compared to dedicated solutions. The Github trending for Vector Databases https://github.com/topics/vector-database https://github.com/topics/vector-database