10 ms·
As someone who just indexed 6m documents with pgvector, I can say it’s a massive time sync - on the order of days, even with a 32 core 64Gb RDS instance.
by lettergram 3y ago
As someone who just indexed 6m documents with pgvector, I can say it’s a massive time sync - on the order of days, even with a 32 core 64Gb RDS instance.
- cyanydeez 3y agowhat was the token sizes for comparison?
- lettergram 3y agoI've done a few 384, 762, 512 all take a few days Though index creation is not a big deal, I want good queries rapidly for cheap. So IMO RDS with pgvector is the easiest approach.
- jn2clark 3y agoThat sounds much longer than it should. I am not sure on your exact use-case but I would encourage you to check out Marqo (https://github.com/marqo-ai/marqo https://github.com/marqo-ai/marqo - disclaimer, I am a co-founder). All inference and orchestration is included (no api calls) and many open-source or fine-tuned models can be used.
- chatmasta 3y ago> That [pgvector index creation time] sounds much longer than it should... I would encourage you to check out Marqo Your comment makes it sound like Marqo is a way to speed up pgvector indexing, but to be clear, Marqo is just another Vector Database and is unrelated to pgvector.
- jn2clark 3y agoFair enough, apologies for the confusion!
- code_biologist 3y agoThe reason I would use pgvector is because I am uninterested in another piece of infrastructure.