Indexing 100M vectors in 20 minutes on PostgreSQL with 12GB RAM
blog.vectorchord.ai
Indexing 100M vectors in 20 minutes on PostgreSQL with 12GB RAM
1–10 of 27 posts
Re: Indexing 100M vectors in 20 minutes on PostgreSQL with 12GB RAM
#2Re: Indexing 100M vectors in 20 minutes on PostgreSQL with 12GB RAM
#3Kinda makes you wonder why you need cloud for anything besides remote encrypted backups if you can run all that on 12GB
Re: Indexing 100M vectors in 20 minutes on PostgreSQL with 12GB RAM
#4Re: Indexing 100M vectors in 20 minutes on PostgreSQL with 12GB RAM
#5Kinda makes you wonder why you need cloud for anything besides remote encrypted backups if you can run all that on 12GB
Re: Indexing 100M vectors in 20 minutes on PostgreSQL with 12GB RAM
#6You must have the data upfront, you cannot build this in an incremental fashion
There is also bo mention on how this would handle updates, and from the description, even if updates are possible, this will degrade over time, requiring new indexing batch
Re: Indexing 100M vectors in 20 minutes on PostgreSQL with 12GB RAM
#7Kinda makes you wonder why you need cloud for anything besides remote encrypted backups if you can run all that on 12GB
what about failover story if server dies? PG failover setup is complicated, and cloud infra handles this for you.
Re: Indexing 100M vectors in 20 minutes on PostgreSQL with 12GB RAM
#8Kinda makes you wonder why you need cloud for anything besides remote encrypted backups if you can run all that on 12GB
Because getting any hardware out of infra-team on premise is utterly miserable, across the board.
Rent your VPS and add in extra volumes for like $10 per 100GB.
Re: Indexing 100M vectors in 20 minutes on PostgreSQL with 12GB RAM
#9Earlier quoted context omitted.
what about failover story if server dies? PG failover setup is complicated, and cloud infra handles this for you.
Do we mean managed or PG on K8s like CNPG? In all cases, I use the infra to simplify things like having disk redundancy and failover nodes, not because 12GB is interesting.