From 0fa6ff954f5a3ab6f203719b3d2509b90c5f86a8 Mon Sep 17 00:00:00 2001 From: kartik-gupta-ij Date: Mon, 13 May 2024 14:19:36 +0530 Subject: [PATCH] docs: remove cloud handle shard rebalancing from FAQ --- .../content/documentation/faq/qdrant-fundamentals.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/qdrant-landing/content/documentation/faq/qdrant-fundamentals.md b/qdrant-landing/content/documentation/faq/qdrant-fundamentals.md index ba983b62a..12185abb7 100644 --- a/qdrant-landing/content/documentation/faq/qdrant-fundamentals.md +++ b/qdrant-landing/content/documentation/faq/qdrant-fundamentals.md @@ -91,8 +91,4 @@ Memory usage in fastEmbed depends on several factors: 2. **Data Parallelism**: fastEmbed utilizes Python's multiprocessing to split large lists of strings into smaller ones and process them in parallel. While this enhances processing speed, it can also lead to higher RAM consumption. 3. **Model Used**: Memory usage varies depending on the model used to embed your data. -For optimal performance and memory management, consider these factors when using fastEmbed. - -### How does your cloud handle shard rebalancing when increasing the number of nodes? - -Our [cloud platform](https://cloud.qdrant.io) handles shard rebalancing when scaling out. However, it's essential to create enough shards beforehand to facilitate the scaling process effectively. For instance, if you have 3 nodes, it's advisable to choose 6 or 9 shards to allow for rebalancing upon extending your cluster, which wouldn't be possible with just 3 shards. \ No newline at end of file +For optimal performance and memory management, consider these factors when using fastEmbed. \ No newline at end of file