Use memmap_threshold instead of memmap_threshold_kb (#1254)

This commit is contained in:
Bastian Hofmann
2024-10-25 17:35:22 -03:00
committed by GitHub
parent a561499b56
commit 518fc722d5
5 changed files with 8 additions and 8 deletions
@@ -110,7 +110,7 @@ memmaps may be enabled on a per-vector basis using the `on_disk` parameter. This
will store vector data directly on disk at all times. It is suitable for
ingesting a large amount of data, essential for the billion scale benchmark.
Using `memmap_threshold_kb` is not recommended in this case. It would require
Using `memmap_threshold` is not recommended in this case. It would require
the [optimizer](/documentation/concepts/optimizer/) to constantly
transform in-memory segments into memmap segments on disk. This process is
slower, and the optimizer can be a bottleneck when ingesting a large amount of