From f1fe6bdb35d7cf17b2d60ca57357e6f27ec99ec0 Mon Sep 17 00:00:00 2001 From: Mike Jang Date: Tue, 21 Nov 2023 13:31:03 -0800 Subject: [PATCH] Update qdrant-landing/content/documentation/concepts/collections.md --- qdrant-landing/content/documentation/concepts/collections.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/qdrant-landing/content/documentation/concepts/collections.md b/qdrant-landing/content/documentation/concepts/collections.md index d2f3e6f69..366e0557f 100644 --- a/qdrant-landing/content/documentation/concepts/collections.md +++ b/qdrant-landing/content/documentation/concepts/collections.md @@ -25,7 +25,7 @@ These settings can be changed at any time by a corresponding request. ## Setting up multitenancy -**How many collections should you create?** In most cases, you should only use a single collection with payload-based partitioning. This approach is called [multitenancy](https://www.ibm.com/topics/multi-tenant). It is efficient for most of users, but it requires additional configuration. [Learn how to set it up](../../tutorials/multiple-partitions/) +**How many collections should you create?** In most cases, you should only use a single collection with payload-based partitioning. This approach is called [multitenancy](https://en.wikipedia.org/wiki/Multitenancy). It is efficient for most of users, but it requires additional configuration. [Learn how to set it up](../../tutorials/multiple-partitions/) **When should you create multiple collections?** When you have a limited number of users and you need isolation. This approach is flexible, but it may be more costly, since creating numerous collections may result in resource overhead. Also, you need to ensure that they do not affect each other in any way, including performance-wise.