Re:90x Faster Than Pgvector – Lantern's HNSW Index Creation ...
by lettergram on Tuesday January 02, 2024 @04:10PM
(#38847202)
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.
[ Parent
| on HN ]
Re:90x Faster Than Pgvector – Lantern's HNSW Index Creation ...
by cyanydeez on Tuesday January 02, 2024 @04:40PM
(#38847477)
what was the token sizes for comparison?
Re:90x Faster Than Pgvector – Lantern's HNSW Index Creation ...
by lettergram on Tuesday January 02, 2024 @04:43PM
(#38847509)
I'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.
Re:90x Faster Than Pgvector – Lantern's HNSW Index Creation ...
by jn2clark on Tuesday January 02, 2024 @04:56PM
(#38847629)
That 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 - 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.
Re:90x Faster Than Pgvector – Lantern's HNSW Index Creation ...
by chatmasta on Tuesday January 02, 2024 @04:58PM
(#38847654)
> 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.
Re:90x Faster Than Pgvector – Lantern's HNSW Index Creation ...
by jn2clark on Tuesday January 02, 2024 @06:01PM
(#38848265)
Fair enough, apologies for the confusion!
Re:90x Faster Than Pgvector – Lantern's HNSW Index Creation ...
by code_biologist on Tuesday January 02, 2024 @05:05PM
(#38847724)
The reason I would use pgvector is because I am uninterested in another piece of infrastructure.