Quotas and limits in Compute Cloud
Compute Cloud has the following limits:
- Quotas
are organizational restrictions that can be changed by technical support. - Limits are technical limitations due to Yandex Cloud architectural features. You cannot change the limits.
If you need more resources, you can increase quotas in one of the following ways:
- Generate a request for a quota increase
. You must have thequota-manager.requestOperator
role or higher, such aseditor
oradmin
. - Contact technical support
and tell us which quotas you want increased and by how much.
Quotas
Type of limit | Value |
---|---|
Number of virtual machines per cloud | 12 |
Total number of vCPUs across all VMs per cloud | 32 |
Total number of vCPUs across all VMs per cloud per ru-central1-c zone | 0 |
Total number of Intel Ice Lake Compute-Optimized vCPUs across all VMs per cloud | 0 |
Total virtual memory across all VMs per cloud | 128 GB |
Total number of disks per cloud | 32 |
Total number of disks per cloud per ru-central1-c zone | 0 |
Total HDD storage capacity per cloud | 500 GB |
Total SSD storage capacity per cloud | 200 GB |
Total non-replicated SSD storage capacity per cloud | 558 GB |
Total capacity of ultra high-speed network SSD storages with three replicas per cloud | 186 GB |
Number of non-replicated disk placement groups per cloud | 5 |
Total number of disk snapshots per cloud | 32 |
Total storage capacity of all disk snapshots per cloud | 400 GB |
Number of disk snapshot schedules per cloud | 32 |
Total number of file storages per cloud1 | 100 |
Total number of file storages per cloud per ru-central1-c zone | 0 |
Total HDD file storage capacity per cloud1 | 0 B |
Total SDD file storage capacity per cloud1 | 0 B |
Number of images per cloud | 8 |
Number of images optimized for deployment per cloud1 | 0 |
Number of instance groups per cloud | 10 |
Total number of NVIDIA® Tesla® V100 GPUs across all VMs per cloud | 0 |
Total number of AMD EPYC™ with NVIDIA® Ampere® A100 GPUs across all VMs per cloud | 0 |
Total number of Intel Ice Lake with NVIDIA® Tesla® T4 GPUs across all VMs per cloud | 0 |
Number of concurrent operations per folder | 15 |
Maximum number of VM placement groups per cloud | 2 |
Maximum number of VMs per partition in a VM placement group with the partition placement strategy | 100 |
Number of dedicated hosts per dedicated host group1 | 0 |
Number of dedicated host groups per cloud | 6 |
Maximum number of VM network interfaces | 8 |
1 To increase quotas
VM limits
Limits per VM depend on the VM platform:
Type of limit | Value |
---|---|
Maximum number of vCPUs per VM | 32 |
Maximum virtual memory per VM | Without GPU: 256 GB With GPU: 384 GB |
Maximum number of disks and file storages attached to a single VM2 | 18 vCPUs or fewer: 8 More than 18 vCPUs: 163 |
Maximum number of GPUs connected to a single VM | 4 |
Maximum number of security groups per interface | 5 |
Maximum number of VMs per VM placement group with the spread placement strategy | 5 |
Type of limit | Value |
---|---|
Maximum number of vCPUs per VM | Without GPU: 80 With GPU: 64 |
Maximum virtual memory per VM | Without GPU: 1280 GB With GPU: 384 GB |
Maximum number of disks and file storages attached to a single VM2 | 20 vCPUs or fewer: 8 More than 20 vCPUs: 163 |
Maximum number of GPUs connected to a single VM | 8 |
Maximum number of security groups per interface | 5 |
Maximum number of VMs per VM placement group with the spread placement strategy | 5 |
Type of limit | Value |
---|---|
Maximum number of vCPUs per VM | 96 |
Maximum virtual memory per VM | 640 GB |
Maximum number of disks and file storages attached to a single VM2 | 32 vCPUs or fewer: 8 More than 32 vCPUs: 163 |
Maximum number of security groups per interface | 5 |
Maximum number of VMs per VM placement group with the spread placement strategy | 5 |
Type of limit | Value |
---|---|
Maximum number of vCPUs per VM | 56 |
Maximum virtual memory per VM | 448 GB |
Maximum number of disks and file storages attached to a single VM2 | 32 vCPUs or fewer: 8 More than 32 vCPUs: 163 |
Maximum number of security groups per interface | 5 |
Maximum number of VMs per VM placement group with the spread placement strategy | 5 |
2 Including the boot disk.
3 When a VM starts, a maximum of 14 devices, including the boot disk and a NIC, can be connected to it. You should connect other devices when your VM is already running. Please note that if you restart a VM with more than 14 devices connected, it will not be able to boot.
VM limits on disk operations
Disk and file storage limits
Type of limit | Value |
---|---|
Maximum disk size | 256 TB |
Allocation unit size | 32 GB |
Maximum4 IOPS for writes per disk | 40,000 |
Maximum4 IOPS for writes per allocation unit | 1,000 |
Maximum5 bandwidth for writes per disk | 450 MB/s |
Maximum5 bandwidth for writes per allocation unit | 15 MB/s |
Maximum4 IOPS for reads per disk | 20,000 |
Maximum4 IOPS for reads per allocation unit | 1,000 |
Maximum5 bandwidth for reads per disk | 450 MB/s |
Maximum5 bandwidth for reads per allocation unit | 15 MB/s |
Type of limit | Value |
---|---|
Maximum disk size | 256 TB |
Allocation unit size | 256 GB |
Maximum4 IOPS for writes per disk | 11,000 |
Maximum4 IOPS for writes per allocation unit | 300 |
Maximum5 bandwidth for writes per disk | 240 MB/s |
Maximum5 bandwidth for writes per allocation unit | 30 MB/s |
Maximum4 IOPS for reads per disk | 2,000 |
Maximum4 IOPS for reads per allocation unit | 300 |
Maximum5 bandwidth for reads per disk | 240 MB/s |
Maximum5 bandwidth for reads per allocation unit | 30 MB/s |
Type of limit | Value |
---|---|
Minimum non-replicated disk size | 93 GB |
Allocation unit size | 93 GB |
Maximum4 IOPS for writes per disk | 75,000 |
Maximum4 IOPS for writes per allocation unit | 5,600 |
Maximum5 bandwidth for writes per disk | 1 GB/s |
Maximum5 bandwidth for writes per allocation unit | 82 MB/s |
Maximum4 IOPS for reads per disk | 75,000 |
Maximum4 IOPS for reads per allocation unit | 28,000 |
Maximum5 bandwidth for reads per disk | 1 GB/s |
Maximum5 bandwidth for reads per allocation unit | 110 MB/s |
Type of limit | Value |
---|---|
Minimum capacity of ultra high-speed network storage with three replicas (SSD) | 93 GB |
Allocation unit size | 93 GB |
Maximum4 IOPS for writes per disk | 40,000 |
Maximum4 IOPS for writes per allocation unit | 5,600 |
Maximum5 bandwidth for writes per disk | 1 GB/s |
Maximum5 bandwidth for writes per allocation unit | 82 MB/s |
Maximum4 IOPS for reads per disk | 75,000 |
Maximum4 IOPS for reads per allocation unit | 28,000 |
Maximum5 bandwidth for reads per disk | 1 GB/s |
Maximum5 bandwidth for reads per allocation unit | 110 MB/s |
Type of limit | Value |
---|---|
Maximum storage size | 8 TB |
Allocation unit size | 32 GB |
Maximum number of files in storage | 1,000,000 |
Maximum size of file in storage | 300 GB |
Type of limit | Value |
---|---|
Maximum storage size | 8 TB |
Allocation unit size | 256 GB |
Maximum number of files in storage | 1,000,000 |
Maximum size of file in storage | 300 GB |
Read and write operations utilize the same disk resource. The more read operations you do, the fewer write operations you can do, and vice versa. For more information, see Read and write operations.
4 To achieve maximum IOPS, we recommend performing read and write operations whose size is close to that of the disk block (4 KB by default).
5 To achieve the maximum possible bandwidth, we recommend performing 4 MB reads and writes.
Limits of disk snapshot schedules
Type of limit | Value |
---|---|
Number of disks added to a schedule | 1,000 |
Number of schedules a disk is added to | 1,000 |
Other limits
Type of limit | Value |
---|---|
Time to complete processes when stopping a VM6 | 30 seconds |
6 When a VM stops, the hypervisor sends a shutdown signal to the VM operating system. The OS needs to terminate the current processes nice and easy within the next 30 seconds to avoid data loss. After this time elapses, the VM process is forced to stop.