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

Apply review suggestion

Browse Source 
Co-Authored-By: Abdon Pijpelink <abdon.pijpelink@qdrant.com>
This commit is contained in:
timvisee
2026-04-08 17:01:48 +02:00
co-authored by Abdon Pijpelink
parent e21538c473
commit c0f85b6ff7
2 changed files with 8 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/manage-data/indexing.md
+4 -5
View File
@@ -72,11 +72,10 @@ filters to `true`:
| `false` | `true` | Parameterized integer index |
| `false` | `false` | No integer index |
The parameterized index may help to tune and reduce memory usage in collections
with millions of points. We encourage you to try it out if mutual exclusively
using range or lookup payload filter types. If you don't see an improvement or
if you're not sure what kind of payload filters you're using, you can always go
back the regular `integer` index.
Setting `lookup` or `range` to `false` may help to tune and reduce memory usage
in large collections. We encourage you to try out if setting either to `false`
improves memory usage. If you don't see an improvement or if you're not sure
what kind of payload filters you're using, use the regular `integer` index.
Note: If you set `"range": false` and still use a range filter, it may lead to
significant performance issues. The same is true for the lookup parameter and
qdrant-landing/static/llms-full.txt
+4 -5
View File
@@ -28171,11 +28171,10 @@ filters to `true`:
| `false` | `true` | Parameterized integer index |
| `false` | `false` | No integer index |
The parameterized index may help to tune and reduce memory usage in collections
with millions of points. We encourage you to try it out if mutual exclusively
using range or lookup payload filter types. If you don't see an improvement or
if you're not sure what kind of payload filters you're using, you can always go
back the regular `integer` index.
Setting `lookup` or `range` to `false` may help to tune and reduce memory usage
in large collections. We encourage you to try out if setting either to `false`
improves memory usage. If you don't see an improvement or if you're not sure
what kind of payload filters you're using, use the regular `integer` index.
Note: If you set `"range": false` and still use a range filter, it may lead to
significant performance issues. The same is true for the lookup parameter and