I have been playing with Milvus but as my use case evolves, I think PGVector may be a better fit . I currently store a lot of enriched data in PG and embeddings in Milvus. Consolidating them into one DB makes sense to me.
We're using PG vector alongside our other dat. It's has pros and cons. I've found checking to be really slow, so we don't index vectors. We just make sure the query filters down on a small enough subset where a direct comparison is good enough.
The other thing we've encountered is that vectors take up a lot of storage space compared to the normal columns (easily a couple kb per row). You can fill up a db really quickly, especially if you're embedding really small chunks
Comments
I have been playing with Milvus but as my use case evolves, I think PGVector may be a better fit . I currently store a lot of enriched data in PG and embeddings in Milvus. Consolidating them into one DB makes sense to me.
We're using PG vector alongside our other dat. It's has pros and cons. I've found checking to be really slow, so we don't index vectors. We just make sure the query filters down on a small enough subset where a direct comparison is good enough.
The other thing we've encountered is that vectors take up a lot of storage space compared to the normal columns (easily a couple kb per row). You can fill up a db really quickly, especially if you're embedding really small chunks
You should take a look at qdrant then. Might fit your use case