mirror of
https://github.com/qdrant/landing_page.git
synced 2026-10-04 10:28:29 +02:00
Clarified that you can only add 1 gpu
This commit is contained in:
@@ -78,7 +78,7 @@ This page shows you how to use the Qdrant Cloud Console to create a custom Qdran
|
||||
1. Configure RAM for each node.
|
||||
> For more information, see our [Capacity Planning](/documentation/operations/capacity-planning/) guidance.
|
||||
1. Choose the number of vCPUs and GPUs per node. If you add more
|
||||
RAM, the menu provides different options for vCPUs. For higher RAM configurations, you can also choose to add GPUs to optimize indexing performance (AWS only).
|
||||
RAM, the menu provides different options for vCPUs. For higher RAM configurations, you can also choose to add a GPU to optimize indexing performance (AWS only).
|
||||
1. Select the number of nodes you want the cluster to be deployed on.
|
||||
> Each node is automatically attached with a disk, that has enough space to store data with Qdrant's default collection configuration.
|
||||
1. Select additional disk space for your deployment.
|
||||
@@ -108,7 +108,7 @@ We recommend the **Balanced** tier for disks >= 32 GiB, and the **Performance**
|
||||
|
||||
**GPUs (AWS only)**
|
||||
|
||||
If you have a write-heavy workload, you can add GPUs to optimize indexing performance. See [**GPUs for Indexing**](/documentation/operations/running-with-gpu/) for more information. All GPU settings will be configured automatically by the cloud platform.
|
||||
If you have a write-heavy workload, you can add a GPU to each node to optimize indexing performance. See [**GPUs for Indexing**](/documentation/operations/running-with-gpu/) for more information. All GPU settings will be configured automatically by the cloud platform.
|
||||
|
||||
**Backup and Disaster Recovery**
|
||||
|
||||
|
||||
Reference in New Issue
Block a user