From 6b109a471c811ae274bc2771c2bbaba3917ea0d5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ramiro=20Nu=C3=B1ez=20Dosio?= Date: Thu, 13 Jul 2023 13:46:05 +0100 Subject: [PATCH] Update apps/www/_blog/2023-07-13-pgvector-performance.mdx Co-authored-by: egor <58992960+egor-romanov@users.noreply.github.com> --- apps/www/_blog/2023-07-13-pgvector-performance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/www/_blog/2023-07-13-pgvector-performance.mdx b/apps/www/_blog/2023-07-13-pgvector-performance.mdx index 80a4d95c92a..ccf7f7448c4 100644 --- a/apps/www/_blog/2023-07-13-pgvector-performance.mdx +++ b/apps/www/_blog/2023-07-13-pgvector-performance.mdx @@ -1,6 +1,6 @@ --- title: 'pgvector 0.4.0 performance' -description: There are a few pgvector benchmarks floating around the internet, most recently a pgvector vs Qdrant comparison. We wanted to reproduce (or improve!) the results. +description: There's been lot of talk about pgvector performance lately, so we took some datasets and pushed pgvector to the limits to find out its strengths and limitations. tags: - AI - performance