krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-09-29 16:08:32 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: Correct segment merging documentation

Browse Source
This commit is contained in:
Dorsa Hasanlee
2024-08-27 22:37:33 +03:30
committed by GitHub
parent 0fbe0545e6
commit 1ab170f97a
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/concepts/optimizer.md
+3 -3
View File
@@ -50,7 +50,7 @@ Such segments, for example, are created as copy-on-write segments during optimiz
It is also essential to have at least one small segment that Qdrant will use to store frequently updated data. It is also essential to have at least one small segment that Qdrant will use to store frequently updated data.
On the other hand, too many small segments lead to suboptimal search performance. On the other hand, too many small segments lead to suboptimal search performance.
There is the Merge Optimizer, which combines the smallest segments into one large segment. It is used if too many segments are created. Qdrant uses a parameter called max_segment_size to control the size of segments. Increasing this value allows the creation of larger segments, reducing the number of segments and potentially improving search performance.
The criteria for starting the optimizer are defined in the configuration file. The criteria for starting the optimizer are defined in the configuration file.
@@ -59,8 +59,8 @@ Here is an example of parameter values:
```yaml ```yaml
storage: storage:
optimizers: optimizers:
# If the number of segments exceeds this value, the optimizer will merge the smallest segments. # This parameter defines the maximum size of a segment. Increasing this value can help in reducing the number of segments.
max_segment_number: 5 max_segment_size: <desired_size>
``` ```
## Indexing Optimizer ## Indexing Optimizer