hey hn, supabase ceo here this is a response to a recent pgvector vs qdrant benchmark. As we mention in the post, we’re not trying to prove that pgvector is fa

hey hn, supabase ceo here this is a response to a recent pgvector vs qdrant benchmark. As we mention in the post, we’re not trying to prove that pgvector is faster than Qdrant. Our goal is to show that pgvector/postgres scales predictably for the workloads that most companies need. We scale it to ~1800 requests per second with 91% precision in this set of benchmarks. Still, it could be better. Luckily there are quite a few features and improvements planned for v0.5.0 [0]: - Adding HNSW: an index with better speed & precision than IVFFlat (at a higher memory cost) - Product quantization: better storage for IVFFLAT, improving speed and recall - Parallel index builds: building your IVFFLAT indexes will be much faster [0]: pgvector v0.5: https://github.com/pgvector/pgvector/issues/27 https://github.com/pgvector/pgvector/issues/27