From c33c4e3471b99f0f44ee9fe71539e0315b913198 Mon Sep 17 00:00:00 2001 From: David Myriel Date: Thu, 26 Sep 2024 18:56:04 -0700 Subject: [PATCH] Update qdrant-landing/content/documentation/guides/capacity-planning.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Tim Visée --- .../content/documentation/guides/capacity-planning.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/qdrant-landing/content/documentation/guides/capacity-planning.md b/qdrant-landing/content/documentation/guides/capacity-planning.md index 7b8a6b921..23d0494f0 100644 --- a/qdrant-landing/content/documentation/guides/capacity-planning.md +++ b/qdrant-landing/content/documentation/guides/capacity-planning.md @@ -83,6 +83,8 @@ In this scenario, only the active subset of vectors will be cached in RAM, allow memory_size = number_of_active_vectors * vector_dimension * 4 bytes * 1.5 ``` +Please refer to our [multitenancy](/documentation/guides/multiple-partitions/) documentation for more details on partitioning data in a Qdrant. + ## Scaling disk space in Qdrant Cloud Clusters supporting vector search require substantial disk space. If you're running low on disk space, you can use the UI at [cloud.qdrant.io](https://cloud.qdrant.io/) to **Scale Up** your cluster.