News for hackers. Stuff that matters.
Re:Pgvector 0.4.0 Performance by andre-z on Thursday July 13, 2023 @01:38PM (#36713038)
Hey, qdrant ceo here. Paul, you and your team are building amazing open-source tech! And, of course, you can scale (almost) anything with just more hardware. As Nirant mentioned in his Twitter response. https://twitter.com/NirantK/status/1679525251213066245 So, it is not only a question of performance but also efficiency.

PS: What about offering Qdrant as an alternative to PG on the supabase platform? Just an idea. :)

Re:Pgvector 0.4.0 Performance by egorr on Thursday July 13, 2023 @01:47PM (#36713192)
i am not Paul of course, but i just want to highlight that the idea behind blogpost was to show that if you set some settings for postgres correctly, you can achieve much better performance

ie you can notice that most of results are on the same hardware as in nirantk, and we achieved 7 times better RPS with 0.98 precision on it and 19 times better RPS with 0.91 precision on the same amount of cpu and memory

goal was to compare pgvector with pgvector rather than any other technology

Re:Pgvector 0.4.0 Performance by kiwicopple on Thursday July 13, 2023 @02:34PM (#36713981)
> What about offering Qdrant as an alternative to PG on the supabase platform

We are "all in" on Postgres, but we could definitely find ways to support qdrant (probably a Wrapper: https://supabase.com/blog/postgres-foreign-data-wrappers-rus...)