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

Merge pull request #2544 from qdrant/sizing-calculator-update

Browse Source 
Update sizing calculator links
This commit is contained in:
kanungle
2026-07-28 07:55:39 -07:00
committed by GitHub
parent 00b9679250 60039c3a67
commit 03760ea48a
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/capacity-planning.md
+1 -1
View File
@@ -20,7 +20,7 @@ When setting up your cluster, you'll need to figure out the right balance of **R
- Your cluster's replication settings.
- Whether you're using quantization and how you’ve set it up.
<aside role="status">To estimate your collection footprint interactively, try the <a href="https://sizing.qdrant.tech/estimate">Qdrant Sizing Calculator</a>.</aside>
<aside role="status">To estimate your collection footprint interactively, try the <a href="https://sizing.qdrant.tech/">Qdrant Sizing Calculator</a>.</aside>
## Calculating RAM size
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.