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

update links

Browse Source
This commit is contained in:
kanungle
2026-07-27 14:43:40 -07:00
parent fc3af21094
commit 7e7602b3dd
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/articles/bulk-uploads-in-qdrant.md
+1 -1
View File
@@ -251,4 +251,4 @@ The safest approach is to choose the right strategy for the workload instead of
> **Tip:** After a large upload, confirm the collection status is green and the optimizers have finished before serving production traffic.
By designing the collection and upload process before ingestion starts, you can make bulk uploads more efficient, more stable, and easier to scale as your dataset grows. To size your deployment, use the [Qdrant sizing calculator](https://sizing.qdrant.tech/estimate).
By designing the collection and upload process before ingestion starts, you can make bulk uploads more efficient, more stable, and easier to scale as your dataset grows. To size your deployment, use the [Qdrant sizing calculator](http://sizing.qdrant.tech/).
qdrant-landing/content/documentation/scaling/vertical-scaling.md
+1 -1
View File
@@ -48,7 +48,7 @@ num_vectors * dimensions * 4 bytes * 1.5
Quantization can reduce this estimate by a factor of 4 to 32, depending on the quantization method. See [Quantization](/documentation/manage-data/quantization/) for the tradeoffs between quantization methods, and monitor actual memory usage before and after resizing (see [Monitor Collection Memory Usage](/documentation/ops-monitoring/memory-usage/)).
<aside role="status">To get a more detailed sizing estimate, try the <a href="https://sizing.qdrant.tech/estimate">Qdrant Sizing Calculator</a>.</aside>
<aside role="status">To get a more detailed sizing estimate, try the <a href="https://sizing.qdrant.tech/">Qdrant Sizing Calculator</a>.</aside>
On top of the vector data itself, budget for the HNSW index, which typically adds 20% to 30% overhead, along with payload indexes and the write-ahead log. Reserve about 20% headroom for optimizer operations and operating system cache.