From d04ec0b75a659837ed48bf17acdf60fb89a0fb0d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Istv=C3=A1n=20Zolt=C3=A1n=20Szab=C3=B3?= Date: Tue, 2 Jun 2026 13:16:14 +0200 Subject: [PATCH] Apply suggestions from code review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: István Zoltán Szabó --- qdrant-landing/content/documentation/overview/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/qdrant-landing/content/documentation/overview/_index.md b/qdrant-landing/content/documentation/overview/_index.md index 310768a59..5433596c9 100644 --- a/qdrant-landing/content/documentation/overview/_index.md +++ b/qdrant-landing/content/documentation/overview/_index.md @@ -114,7 +114,7 @@ Vertical scaling has natural limits \- eventually, you'll hit the maximum capaci Qdrant uses sharding to split collections across multiple nodes, where each shard is an independent store of points. A common recommendation is to start with 12 shards, which provides flexibility to scale from 1 node up to 2, 3, 6, or 12 nodes without resharding. However, this approach can limit throughput on small clusters since each node manages multiple shards. -For optimal throughput, set `shard_number` equal to your node count (read more [here](/documentation/distributed_deployment#sharding)). If you want to have better control over sharding, Qdrant supports [custom shards](/documentation/distributed_deployment/#user-defined-sharding). +For optimal throughput, set `shard_number` equal to your node count (read more [here](/documentation/distributed_deployment/#sharding)). If you want to have better control over sharding, Qdrant supports [custom shards](/documentation/distributed_deployment/#user-defined-sharding). #### Replication {#replication}