From b3f4b1ac247e05657890d3fec875631bc450ff65 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tim=20Vis=C3=A9e?= Date: Wed, 27 Nov 2024 16:42:48 +0100 Subject: [PATCH] Update configuration to match qdrant/qdrant --- .../documentation/concepts/optimizer.md | 21 +++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) diff --git a/qdrant-landing/content/documentation/concepts/optimizer.md b/qdrant-landing/content/documentation/concepts/optimizer.md index c2fca98c6..0d276125d 100644 --- a/qdrant-landing/content/documentation/concepts/optimizer.md +++ b/qdrant-landing/content/documentation/concepts/optimizer.md @@ -59,8 +59,25 @@ Here is an example of parameter values: ```yaml storage: optimizers: - # This parameter defines the maximum size of a segment. Increasing this value can help in reducing the number of segments. - max_segment_size: + # Target amount of segments optimizer will try to keep. + # Real amount of segments may vary depending on multiple parameters: + # - Amount of stored points + # - Current write RPS + # + # It is recommended to select default number of segments as a factor of the number of search threads, + # so that each segment would be handled evenly by one of the threads. + # If `default_segment_number = 0`, will be automatically selected by the number of available CPUs + default_segment_number: 0 + + # Do not create segments larger this size (in KiloBytes). + # Large segments might require disproportionately long indexation times, + # therefore it makes sense to limit the size of segments. + # + # If indexation speed have more priority for your - make this parameter lower. + # If search speed is more important - make this parameter higher. + # Note: 1Kb = 1 vector of size 256 + # If not set, will be automatically selected considering the number of available CPUs. + max_segment_size_kb: null ``` ## Indexing Optimizer