From c480db599f17639a686abc43a22f982ea2869ae3 Mon Sep 17 00:00:00 2001 From: Copple <10214025+kiwicopple@users.noreply.github.com> Date: Thu, 13 Jul 2023 15:00:38 +0200 Subject: [PATCH] Update apps/www/_blog/2023-07-13-pgvector-performance.mdx --- 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 6df5833af37..6493a5ef712 100644 --- a/apps/www/_blog/2023-07-13-pgvector-performance.mdx +++ b/apps/www/_blog/2023-07-13-pgvector-performance.mdx @@ -150,7 +150,7 @@ Another key takeaway is that the performance scales predictably with the size of
-Again, it is NOT our goal to prove that pgvector is better than Qdrant for running vector workloads. The Qdrant benchmark uses “default” configuration and is in not indicative of its capabilities after modifying the configuration. +The Qdrant benchmark uses “default” configuration and is in not indicative of its capabilities after modifying the configuration.