Which vector database should I use? A comparison cheatsheet
navidre.medium.com
Which vector database should I use? A comparison cheatsheet
1–10 of 91 posts
Re: Which vector database should I use? A comparison cheatsheet
#2I have prepared this comparison table to help me choose a vector database. I am sharing it here, hoping it may assist you in your projects as well. Main comparison points: cost at scale, compliance, and queries per second (QPS).
Re: Which vector database should I use? A comparison cheatsheet
#3I have prepared this comparison table to help me choose a vector database. I am sharing it here, hoping it may assist you in your projects as well. Main comparison points: cost at scale, compliance, and queries per second (QPS).
Wondering why you didn’t include Elasticsearch [0] in your comparison.
Also having some benchmark to compare performance would help.
[0] https://www.elastic.co/guide/en/elasticsearch/reference/curr...
Re: Which vector database should I use? A comparison cheatsheet
#4How do they compare to embeddings in OpenAI? (Sorry I'm new to all this.)
Re: Which vector database should I use? A comparison cheatsheet
#5How do they compare to embeddings in OpenAI? (Sorry I'm new to all this.)
you can use the openai embeddings as your vectors.
Re: Which vector database should I use? A comparison cheatsheet
#6There needs to be a standard for benchmarking performance of these solutions. Milvus qps seems to be in a completely different tier of performance than the rest.
Re: Which vector database should I use? A comparison cheatsheet
#7Missed AstraDB (Cassandra based). It ticks all the green boxes (HIPPA, SOC II, Cloud, in DB etc..)
https://docs.datastax.com/en/astra-serverless/docs/vector-se...
Re: Which vector database should I use? A comparison cheatsheet
#8I like that this comparison shows pg_vector in a positive light. After playing around with a few of the options at my company (graphite.dev), I’m a big fan of the simplicity of Postgres for everything. I understand there’s scaling costs, but being able to treat vectors as simply one more column type is fantastic.
Re: Which vector database should I use? A comparison cheatsheet
#9I have prepared this comparison table to help me choose a vector database. I am sharing it here, hoping it may assist you in your projects as well. Main comparison points: cost at scale, compliance, and queries per second (QPS).
I was looking at Pinecone, but if I'm reading this correctly, several open source vector DBs can pull off the same or better QPS and are open source.
I really hope Pinecone doesn't become the defacto vector DB. They're getting all the attention, but they're closed and crazily venture funded. That's going to turn into an Oracle situation fast.
I understand wanting to keep Amazon out of your business, but licences exist that allow that.
Re: Which vector database should I use? A comparison cheatsheet
#10I have prepared this comparison table to help me choose a vector database. I am sharing it here, hoping it may assist you in your projects as well. Main comparison points: cost at scale, compliance, and queries per second (QPS).
Wondering why you didn’t include Elasticsearch [0] in your comparison. Also having some benchmark to compare performance would help. [0] https://www.elastic.co/guide/en/elasticsearch/reference/curr...
+1, I've been using OpenSearch (basically Elasticsearch 7.0), and have been pretty happy with the setup so far.
OpenSearch specifically has an edge over Elasticsearch because it supports vectors up to 10k dimensions, whereas ES maxes out at indexing 1024 dimensions, which isn't enough to support OpenAI's 1536 dimension vectors.
And then there's the benefit of it being well documented / Q&A'd, and able to support regular searching, faceting, etc. as well.