[Yandex Cloud documentation](../../../index.md) > [Getting started with Yandex Cloud](../../index.md) > Trial period > Trial period restrictions # Trial period restrictions The trial period is available to businesses only as a means of testing and exploring the cloud infrastructure features. During the trial period, you can use Yandex Cloud resources with some restrictions. ## Service Level Agreement (SLA) {#sla} The Service Level Agreement (SLA) does not apply to the trial period. We do not recommend running production applications in Yandex Cloud during the trial period. ## Support {#support} Technical support is provided in full during the trial period. For more information, see [Requesting technical support](../../../support/overview.md). ## Yandex Cloud Billing {#billing} Each cloud in Yandex Cloud must be linked to a single billing account. If you relink an existing cloud, you are effectively transferring it between billing accounts. For legal entities, you cannot relink a cloud and your [DataSphere](../../../datasphere/index.md), [Tracker](https://yandex.com/support/tracker/en), and [DataLens](../../../datalens/index.md) services from a paid account to a trial period account. ## Yandex Cloud Marketplace {#marketplace} During the trial period, no Yandex Cloud Marketplace paid products are available. However, once your paid consumption starts, you will be able to use the balance of your starting grant to pay for them. ## Service quotas and limits {#quotes-and-limits} * [_Quotas_](https://console.yandex.cloud/cloud?section=quotas) are organizational constraints that can be changed by contacting technical support. * _Limits_ are technical constraints of the Yandex Cloud architecture. You cannot change the limits. Quotas and limits for Yandex Cloud services during the trial period are listed below. ### Yandex Compute Cloud {#compute} ## Quotas {#compute-quotas} ### Quotas for instances and instance groups {#vm-quotas} #| || Type of limit | Value || || Number of [virtual machines](../../../compute/concepts/vm.md) per [cloud](../../../resource-manager/concepts/resources-hierarchy.md#cloud) `compute.instances.count` | 12 || || Total virtual memory across all VMs and number of available slots in [reserved instance pools](../../../compute/concepts/reserved-pools.md) per cloud `compute.instanceMemory.size` | 128 GB || || Number of [instance groups](../../../compute/concepts/instance-groups/index.md) per cloud `compute.instanceGroups.count` | 10 || || Maximum number of [VM placement groups](../../../compute/concepts/placement-groups.md) per cloud `compute.placementGroups.count` | 2 || || Maximum number of VMs per partition in a VM placement group with the [partition placement](../../../compute/concepts/placement-groups.md#partition) strategy | 100 || || Maximum number of [security groups](../../../vpc/concepts/security-groups.md) per [network interface](../../../compute/concepts/network.md) {% note warning %} You can increase this quota only upon agreement with your account manager. {% endnote %} | 5 || |# ### vCPU quotas {#vcpu-quotas} #| || Type of limit | Value || || Total number of [vCPUs](../../../compute/concepts/performance-levels.md) across all VMs and number of available slots in reserved instance pools per cloud `compute.instanceCores.count` | 32 || || Total number of Intel Ice Lake Compute-Optimized vCPUs across all VMs and number of available slots in reserved instance pools per cloud `compute.instanceHighFreqCores.count` | 0 || |# ### GPU quotas {#gpu-quotas} #| || Type of limit | Value || || Total number of NVIDIA® Tesla® V100 [GPUs](../../../compute/concepts/gpus.md) across all VMs and number of available slots in reserved instance pools per cloud `compute.instanceGpus.count` | 0 || || Total number of AMD EPYC™ with NVIDIA® Ampere® A100 GPUs across all VMs and number of available slots in reserved instance pools per cloud `compute.instanceA100Gpus.count` | 0 || || Total number of Gen2 GPUs across all VMs and number of available slots in reserved instance pools per cloud `compute.instanceV3IGpus.count` | 0 || || Total number of Intel Ice Lake with NVIDIA® Tesla® T4 GPUs across all VMs and number of available slots in reserved instance pools per cloud `compute.instanceT4Gpus.count` | 0 || || Total number of Intel Ice Lake with NVIDIA® Tesla® T4 GPUs across all VMs and number of available slots in reserved instance pools per cloud in the `ru-central1-d` availability zone `compute.instanceT4Gpus.count.ru-central1-d` | 0 || || Total number of Intel Ice Lake with T4i GPUs across all VMs and number of available slots in reserved instance pools per cloud `compute.instanceT4IGpus.count` | 0 || |# ### Disk quotas {#disk-quotas} #| || Type of limit | Value || || Total number of [disks](../../../compute/concepts/disk.md) per cloud `compute.disks.count` | 32 || || Total [HDD storage](../../../compute/concepts/disk.md#disks-types) capacity per cloud `compute.hddDisks.size` | 500 GB || || Total SSD storage capacity per cloud `compute.ssdDisks.size` | 200 GB || || Total non-replicated SSD storage capacity per cloud `compute.ssdNonReplicatedDisks.size` | 558 GB || || Total capacity of ultra high-speed network SSD storages with three replicas per cloud `compute.ssdIOM3Disks.size` | 186 GB || || Number of [non-replicated disk placement groups](../../../compute/concepts/disk-placement-group.md) per cloud `compute.diskPlacementGroups.count` | 5 || |# ### File storage quotas {#fs-quotas} #| || Type of limit | Value || || Total number of [file storages](../../../compute/concepts/filesystem.md) per cloud `compute.filesystems.count` | 100 || || Total [HDD](../../../compute/concepts/filesystem.md#types) file storage size per cloud `compute.hddFilesystems.size` | 512 GB || || Total SSD file storage size per cloud `compute.ssdFilesystems.size` | 512 GB || |# ### Image quotas {#image-quotas} #| || Type of limit | Value || || Number of [images](../../../compute/concepts/image.md) per cloud `compute.images.count` | 32 || || Total volume of images per cloud `compute.images.size` | 1,024 GB || || Number of [images optimized for deployment](../../../compute/concepts/image.md#images-optimized-for-deployment) per cloud^1^ `compute.diskPools.count` | 0 || |# {% note info %} When deploying optimized images, the quotas for the number of images per cloud and the total volume of images per cloud also apply. If you need to, send a request to [support](https://center.yandex.cloud/support) to increase these quotas. {% endnote %} ### Snapshot quotas {#snapshot-quotas} #| || Type of limit | Value || || Total number of [disk snapshots](../../../compute/concepts/snapshot.md) per cloud `compute.snapshots.count` | 32 || || Total storage capacity of all disk snapshots per cloud `compute.snapshots.size` | 400 GB || || Number of [disk snapshot schedules](../../../compute/concepts/snapshot-schedule.md) per cloud `compute.snapshotSchedules.count` | 32 || |# ### Dedicated host quotas {#dedicated-host-quotas} #| || Type of limit | Value || || Number of [dedicated hosts](../../../compute/concepts/dedicated-host.md) per dedicated host group^1^ `compute.dedicatedHosts.count` | 0 || || Number of dedicated host groups per cloud `compute.hostGroups.count` | 6 || |# ### Other quotas {#compute-other-quotas} #| || Type of limit | Value || || Number of concurrent [operations](../../../api-design-guide/concepts/operation.md) per [folder](../../../resource-manager/concepts/resources-hierarchy.md#folder) | 15 || || Number of [reserved instance pools](../../../compute/concepts/reserved-pools.md) per cloud^1^ `compute.reservedInstancePools.count` | 1 || |# ^1^ To increase [quotas](https://console.yandex.cloud/cloud?section=quotas) for deployment-optimized images, dedicated hosts, or reserved instance pools, contact [support](https://center.yandex.cloud/support). ## Limits {#compute-limits} ### VM limits {#compute-limits-vm} Limits per VM depend on the VM [platform](../../../compute/concepts/vm-platforms.md): {% list tabs group=platforms %} - Intel Broadwell {#broadwell} #| || **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 GPUs connected to a single VM | > | > | 4 || || Maximum number of disks and file storages connected to a single VM^2^ | `PCI_TOPOLOGY_V1` [bus topology](../../../compute/concepts/hardware-generations.md#configurations). | Number of VCPUs <= 18 | 8 || || ^ | ^ | Number of VCPUs > 18 | 16^3^ || || ^ | `PCI_TOPOLOGY_V2` bus topology | Number of VCPUs <= 4 | 62 || || ^ | ^ | Number of VCPUs >= 6 | 80 || || Maximum number of [network interfaces](../../../compute/concepts/network.md) connected to a single VM | Bus topology `PCI_TOPOLOGY_V1` | > | 8^3^ || || ^ | `PCI_TOPOLOGY_V2` bus topology | Number of VCPUs <= 4 | 20 || || ^ | ^ | Number of VCPUs >= 6 | 32 || || Maximum number of VMs per VM placement group with the [spread placement](../../../compute/concepts/placement-groups.md#spread) strategy | > | > | 5 || |# - Intel Cascade Lake {#cascade} #| || **Type of limit** | > | > | **Value** || || Maximum number of vCPUs per VM | > | Without GPU | 80 || || ^ | > | With GPU | 64 || || Maximum virtual memory per VM | > | Without GPU | 1,280 GB || || ^ | > | With GPU | 384 GB || || Maximum number of GPUs connected to a single VM | > | > | 8 || || Maximum number of disks and file storages connected to a single VM^2^ | `PCI_TOPOLOGY_V1` [bus topology](../../../compute/concepts/hardware-generations.md#configurations). | Number of VCPUs <= 20 | 8 || || ^ | ^ | Number of VCPUs > 20 | 16^3^ || || ^ | `PCI_TOPOLOGY_V2` bus topology | Number of VCPUs <= 4 | 62 || || ^ | ^ | Number of VCPUs >= 6 | 80 || || Maximum number of [network interfaces](../../../compute/concepts/network.md) connected to a single VM | Bus topology `PCI_TOPOLOGY_V1` | > | 8^3^ || || ^ | `PCI_TOPOLOGY_V2` bus topology | Number of VCPUs <= 4 | 20 || || ^ | ^ | Number of VCPUs >= 6 | 32 || || Maximum number of VMs per VM placement group with the [spread placement](../../../compute/concepts/placement-groups.md#spread) strategy | > | > | 5 || |# - Intel Ice Lake {#ice} #| || **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 connected to a single VM^2^ | `PCI_TOPOLOGY_V1` [bus topology](../../../compute/concepts/hardware-generations.md#configurations). | Number of VCPUs <= 32 | 8 || || ^ | ^ | Number of VCPUs > 32 | 16^3^ || || ^ | `PCI_TOPOLOGY_V2` bus topology | Number of VCPUs <= 4 | 62 || || ^ | ^ | Number of VCPUs >= 6 | 80 || || Maximum number of [network interfaces](../../../compute/concepts/network.md) connected to a single VM | Bus topology `PCI_TOPOLOGY_V1` | > | 8^3^ || || ^ | `PCI_TOPOLOGY_V2` bus topology | Number of VCPUs <= 4 | 20 || || ^ | ^ | Number of VCPUs >= 6 | 32 || || Maximum number of VMs per VM placement group with the [spread placement](../../../compute/concepts/placement-groups.md#spread) strategy | > | > | 5 || |# - Intel Ice Lake (Compute Optimized) {#optimized} #| || **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 connected to a single VM^2^ | `PCI_TOPOLOGY_V1` [bus topology](../../../compute/concepts/hardware-generations.md#configurations). | Number of VCPUs <= 32 | 8 || || ^ | ^ | Number of VCPUs > 32 | 16^3^ || || ^ | `PCI_TOPOLOGY_V2` bus topology | Number of VCPUs <= 4 | 62 || || ^ | ^ | Number of VCPUs >= 6 | 80 || || Maximum number of [network interfaces](../../../compute/concepts/network.md) connected to a single VM | Bus topology `PCI_TOPOLOGY_V1` | > | 8^3^ || || ^ | `PCI_TOPOLOGY_V2` bus topology | Number of VCPUs <= 4 | 20 || || ^ | ^ | Number of VCPUs >= 6 | 32 || || Maximum number of VMs per VM placement group with the [spread placement](../../../compute/concepts/placement-groups.md#spread) strategy | > | > | 5 || |# {% endlist %} ^2^ Including the boot disk. ^3^ At startup, you can connect no more than 14 devices to a VM, including the boot disk and network card. 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. {% note warning %} To guarantee the operability and performance of VMs with large numbers of disk devices and network interfaces, such numbers of devices and interfaces must be supported not by the VM hardware generation alone but by the OS as well, plus provided with enough vCPUs and RAM. {% endnote %} ### VM limits on disk operations {#compute-limits-vm-disks} {% list tabs group=disks %} - Network SSD {#net-ssd} Type of limit | Value --- | --- Maximum^4^ [IOPS](../../../compute/concepts/storage-read-write.md) per vCPU | 3,500 Maximum^5^ [bandwidth](../../../compute/concepts/storage-read-write.md) per vCPU | 45 MB/s - Network HDD {#net-hdd} Type of limit | Value --- | --- Maximum^4^ [IOPS](../../../compute/concepts/storage-read-write.md) per vCPU | 3,500 Maximum^5^ [bandwidth](../../../compute/concepts/storage-read-write.md) per vCPU | 45 MB/s - Non-replicated SSD {#non-replicated-ssd} Type of limit | Value --- | --- Total number of non-replicated SSDs per placement group | 8 Maximum^4^ [IOPS](../../../compute/concepts/storage-read-write.md) per vCPU | 10,000 Maximum^4^ IOPS per VM | 100,000 Maximum^5^ [bandwidth](../../../compute/concepts/storage-read-write.md) per vCPU | 100 MB/s Maximum^5^ bandwidth per VM | 1 GB/s - Ultra high-speed network storage with three replicas (SSD) {#high-perf-ssd} Type of limit | Value --- | --- Maximum^4^ [IOPS](../../../compute/concepts/storage-read-write.md) per vCPU | 10,000 Maximum^4^ IOPS per VM | 100,000 Maximum^5^ [bandwidth](../../../compute/concepts/storage-read-write.md) per vCPU | 100 MB/s Maximum^5^ bandwidth per VM | 1 GB/s {% endlist %} ### Disk and file storage limits {#compute-limits-disks} {% list tabs group=disks %} - Network SSD {#net-ssd} Type of limit | Value --- | --- Maximum disk size | 256 TB [Allocation unit](../../../compute/concepts/storage-read-write.md) size | 32 GB Maximum^4^ IOPS for writes per disk | 40,000 Maximum^4^ IOPS for writes per allocation unit | 1,000 Maximum^5^ bandwidth for writes per disk | 450 MB/s Maximum^5^ bandwidth for writes per allocation unit | 15 MB/s Maximum^4^ IOPS for reads per disk | 20,000 Maximum^4^ IOPS for reads per allocation unit | 1,000 Maximum^5^ bandwidth for reads per disk | 450 MB/s Maximum^5^ bandwidth for reads per allocation unit | 15 MB/s - Network HDD {#net-hdd} Type of limit | Value --- | --- Maximum disk size | 256 TB [Allocation unit](../../../compute/concepts/storage-read-write.md) size | 256 GB Maximum^4^ IOPS for writes per disk | 11,000 Maximum^4^ IOPS for writes per allocation unit | 300 Maximum^5^ bandwidth for writes per disk | 240 MB/s Maximum^5^ bandwidth for writes per allocation unit | 30 MB/s Maximum^4^ IOPS for reads per disk | 2,000 Maximum^4^ IOPS for reads per allocation unit | 300 Maximum^5^ bandwidth for reads per disk | 240 MB/s Maximum^5^ bandwidth for reads per allocation unit | 30 MB/s - Non-replicated SSD {#non-replicated-ssd} Type of limit | Value --- | --- Minimum non-replicated disk size | 93 GB [Allocation unit](../../../compute/concepts/storage-read-write.md) size | 93 GB Maximum^4^ IOPS for writes per disk | 75,000 Maximum^4^ IOPS for writes per allocation unit | 5,600 Maximum^5^ bandwidth for writes per disk | 1 GB/s Maximum^5^ bandwidth for writes per allocation unit | 82 MB/s Maximum^4^ IOPS for reads per disk | 75,000 Maximum^4^ IOPS for reads per allocation unit | 28,000 Maximum^5^ bandwidth for reads per disk | 1 GB/s Maximum^5^ bandwidth for reads per allocation unit | 110 MB/s - Ultra high-speed network storage with three replicas (SSD) {#high-perf-ssd} Type of limit | Value --- | --- Minimum capacity of ultra high-speed network storage with three replicas (SSD) | 93 GB [Allocation unit](../../../compute/concepts/storage-read-write.md) size | 93 GB Maximum^4^ IOPS for writes per disk | 40,000 Maximum^4^ IOPS for writes per allocation unit | 5,600 Maximum^5^ bandwidth for writes per disk | 1 GB/s Maximum^5^ bandwidth for writes per allocation unit | 82 MB/s Maximum^4^ IOPS for reads per disk | 75,000 Maximum^4^ IOPS for reads per allocation unit | 28,000 Maximum^5^ bandwidth for reads per disk | 1 GB/s Maximum^5^ bandwidth for reads per allocation unit | 110 MB/s {% endlist %} {% list tabs group=storages %} - SSD storage {#ssd} 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 - HDD storage {#hdd} 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 {% endlist %} 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](../../../compute/concepts/storage-read-write.md). ^4^ For maximum IOPS, we recommend keeping your read and write operations close to the disk block size (4 KB by default). ^5^ For maximum bandwidth, we recommend 4 MB reads and writes. ### Limits of disk snapshot schedules {#compute-limits-snapshot-schedule} 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 {#compute-other-limits} Type of limit | Value --- | --- Time to complete processes when stopping a VM^6^ | 30 seconds ^6^ When a VM stops, the hypervisor sends a shutdown signal to the VM operating system. The OS has 30 seconds to gracefully terminate all running processes to avoid data loss. After this time elapses, the VM will be forcibly terminated. ### Yandex Object Storage {#storage} #### Quotas {#storage-quotas} #| || Type of limit | Value || || Storage volume per cloud `storage.volume.size` | 1,024 GB || || Number of buckets per cloud `storage.buckets.count` | 25 || |# #### Limits {#storage-limits} Type of limit | Value --- | --- Maximum object size | 5 TB Total header size per request to HTTP API | 8 KB Size of user-defined metadata in an object | 2 KB Maximum number of rules for [conditional request redirects](../../../storage/operations/hosting/setup.md#redirects-on-conditions) for a website. | 50 Maximum size of data to upload per request | 5 GB Minimum size of data parts for multipart upload, except the last one | 5 MB Maximum number of parts in multipart upload | 10,000 Maximum bucket access policy size | 20 KB ### Yandex Virtual Private Cloud {#vpc} #### Quotas {#vpc-quotas} #| || Type of limit | Value || || Number of cloud networks per cloud `vpc.networks.count` | 2 || || Number of subnets per cloud `vpc.subnets.count` | 12 || || Number of all public IP addresses per cloud `vpc.externalAddresses.count` | 8 || || Number of static public IP addresses per cloud `vpc.externalStaticAddresses.count` | 2 || || Number of routing tables per cloud `vpc.routeTables.count` | 8 || || Number of static routes per cloud `vpc.staticRoutes.count` | 256 || || Maximum number of security groups `vpc.securityGroups.count` | 10 || || Maximum number of security groups per interface | 5 || || Maximum number of service connections per cloud `vpc.privateEndpoints.count` | 2 || |# #### Limits {#vpc-limits} Type of limit | Value ----- | ----- Minimum CIDR size for a subnet | /28 Maximum CIDR size for a subnet | /16 Maximum number of VM connections when using custom security groups^1^ ^2^ | 350,000 Supported network and transport layer protocols | IP, ICMP, TCP, UDP, GRE, ESP, AH Maximum number of rules per security group | 50 Maximum number of CIDRs per rule | 50 Size of the DNS server IP address list | 100 characters Maximum number of DNS requests to a DNS server (second address [in a subnet](../../../vpc/concepts/network.md#subnet)) | 1,000 requests per second Maximum number of NAT gateways | 20 Maximum load per service connection^3^ | 10 Gbps ^1^ Counts all TCP and UDP connections opened and half-opened within 180 seconds. If there are no data or keep-alive packets in the connection during this time, it is forcibly closed. ^2^ The old network diagram had a limit of 50,000 connections. ^3^ If you exceed the limits in place, the platform reserves the right to restrict the service connection. If you need to use your service connections beyond the specified limit, please contact [support](../../../support/overview.md). #### Outgoing traffic filtering {#vpc-egress-traffic-filter} Yandex Cloud automatically blocks traffic sent from Virtual Private Cloud public IP addresses to TCP port 25 of any servers on the internet and Yandex Compute Cloud VMs. The only exception is the traffic sent to Yandex Mail email servers, which is allowed and not blocked. We recommend using [Yandex Cloud Postbox](../../../postbox/index.md) to send your emails. If you have any issues, contact [support](../../../support/overview.md). ### Yandex Resource Manager {#resource-manager} #### Quotas {#resmgr-quotas} #| || Type of limit | Value || || Maximum number of clouds per organization `resource-manager.clouds.count` | 5 || || Maximum number of folders per cloud `resource-manager.folders.count` | 50 || |# #### Limits {#resmgr-limits} There are no limits for Resource Manager. ### Yandex Network Load Balancer {#load-balancer} #### Quotas {#load-balancer-quotas} #| || Type of limitation | Value || || Number of load balancers per cloud `ylb.networkLoadBalancers.count` | 2 || || Number of target groups per cloud `ylb.targetGroups.count` | 100 || |# #### Limits {#load-balancer-limits} Type of limitation | Value ----- | ----- Number of targets per target group | 254 Number of ports per listener | 10 Number of health checks per attached target group | 1 Health check protocol | TCP, HTTP #### Other restrictions {#load-balancer-other-restrictions} A single target group can only contain targets from a single cloud network. Within a single availability zone, a target group can only include targets on the same subnet. If you add a target to the internal load balancer's target group, it will not be directly accessible on the target port. You can create a load balancer without a listener. Health check traffic comes from the `198.18.235.0/24` and `198.18.248.0/24` ranges. When adding targets for a load balancer, keep in mind the [limit](../../../vpc/concepts/limits.md#limits) on the maximum number of concurrent TCP/UDP connections per VM. ### Yandex Managed Service for ClickHouse® {#mch} #### Quotas {#mch-quotas} #| || **Type of limit** | **Value** || || Number of clusters per cloud `mdb.clusters.count` | 16 || || Total number of CPU cores for all database hosts per cloud `mdb.cpu.count` | 64 || || Total virtual memory for all database hosts per cloud `mdb.memory.size` | 512 GB || || Total storage capacity for all clusters per cloud `mdb.ssd.size` | 4,096 GB || || Number of GPUs `mdb.gpu.count` | 0 || |# #### Limits {#mch-limits} #| || **Type of limit** | **Minimum value** | **Maximum value** || || Host class | b1.medium (2 × [50%](../../../compute/concepts/performance-levels.md) vCPUs, Intel Broadwell, 4 GB RAM) | m4a-c224-m1792 (224 vCPU AMD Zen 4, 1,792 GB RAM) || || Number of ClickHouse® hosts per non-sharded cluster when using a network HDD or SSD storage or an ultra high-speed network SSD storage with three replicas | 1 | 7 || || Number of ClickHouse® hosts per non-sharded cluster when using a non-replicated SSD storage | 3 | 7 || || Number of ClickHouse® hosts per non-sharded cluster when using a local SSD storage | 2 | 7 || || Number of shards per sharded cluster | 1 | 100 || || Number of hosts per shard when using a network HDD or SSD storage or an ultra high-speed network SSD storage with three replicas | 1 | 7 || || Number of hosts per shard when using a non-replicated SSD storage | 3 | 7 || || Number of hosts per shard when using a local SSD storage | 2 | 7 || || Total number of hosts per cluster | 1 | 355 (50 shards × 7 hosts + 5 ZooKeeper hosts) || || Amount of data per host when using a network HDD or SSD storage (for Intel Broadwell and Intel Cascade Lake) | 10 GB | 4,096 GB || || Amount of data per host when using a network HDD or SSD storage (for Intel Ice Lake) | 10 GB | 8192 GB || || Amount of data per host when using a non-replicated SSD storage or an ultra high-speed network SSD storage with three replicas | 93 GB | 16,368 GB || || Amount of data per host when using a local SSD storage (for Intel Broadwell and Intel Cascade Lake) | 100 GB | 1500 GB || || Amount of data per host when using a local SSD storage (for Intel Ice Lake and AMD Zen 4) | 368 GB | 5888 GB || || Number of databases per cluster | 1 | 1000 || |# #### Limits on the maximum number of objects {#mch-objects-limits} The limits on the maximum number of objects per cluster have two threshold values: * _Soft limit_: When reached, the `system.warnings` [system table](https://clickhouse.com/docs/enen/operations/system-tables/system_warnings) will display a warning. * _Hard limit_: When reached, creating new objects of this type will end with an error message. {% note info "Note" %} The _hard limit_ threshold only works in ClickHouse® 25.2 and higher. {% endnote %} #| || **Type of limit** | **Soft limit** | **Hard limit** || || Number of databases | 500 | 1,000 || || Number of tables | 5,000 | 10,000 || || Number of views | 5,000 | 10,000 || || Number of external dictionaries | 500 | 1,000 || |# All limits are implemented based on the [ClickHouse® server settings](https://clickhouse.com/docs/enen/operations/server-configuration-parameters/settings). You cannot change them. ### Yandex StoreDoc {#mmg} #### Quotas {#mmg-quotas} #| || Type of limit | Value || || Number of clusters per cloud `mdb.clusters.count` | 16 || || Total number of CPU cores for all database hosts per cloud `mdb.cpu.count` | 64 || || Total virtual memory for all database hosts per cloud `mdb.memory.size` | 512 GB || || Total storage capacity for all clusters per cloud `mdb.ssd.size` | 4,096 GB || || Number of GPUs `mdb.gpu.count` | 0 || |# #### Limits {#mmg-limits} | Type of limit | Minimum value | Maximum value | |:-----------------------------------------------------------------------------------------------------------------|:-------------------------------------------------------------------------------------------------|:-------------------------------------------------| | Host class | b1.medium (2 × [50%](../../../compute/concepts/performance-levels.md) vCPU Intel Broadwell, 4 GB RAM) | m4a-c224-m1792 (224 vCPUs, AMD Zen 4, 1,792 GB RAM) | | Number of shards per cluster | 1 | 10 | | Number of hosts per shard when using a network HDD or SSD storage or an ultra high-speed network SSD storage with three replicas | 1 | 7 | | Number of hosts in a shard when storing data on non-replicated or local SSDs^*^ | 3 | 7 | | Number of hosts per cluster | 1 or 3 hosts depending on the [disk type](../../../storedoc/concepts/storage.md#storage-type-selection); the cluster [is created](../../../storedoc/operations/cluster-create.md) in an unsharded state. | 70 (10 shards × 7 hosts) | | Amount of data per host when using a network HDD or SSD storage. | 10 GB | 2,048 GB | | Amount of data per host when using a non-replicated SSD storage or an ultra high-speed network SSD storage with three replicas | 93 GB | 2,232 GB | | Amount of data per host when using a local SSD storage (for Intel Broadwell and Intel Cascade Lake) | 100 GB | 1,500 GB | | Amount of data per host when using a local SSD storage (for Intel Ice Lake and AMD Zen 4) | 368 GB | 5888 GB | | Number of databases per cluster | 1 | 1000 | ^*^ Read more on how platform selection affects [available storage types](../../../storedoc/concepts/storage.md). The maximum available number of simultaneous connections to a single Yandex StoreDoc cluster host depends on the amount of RAM on the host: | Amount of RAM | Maximum number of connections | | ------------------------:| -----------------------------------:| | 2 GB | 2048 | | 4 GB | 4096 | | 8 GB | 8192 | | 16 GB or higher | 16 384 | ### Yandex Managed Service for MySQL® {#mmy} #### Quotas {#mmy-quotas} #| || Type of limit | Value || || Number of clusters per cloud `mdb.clusters.count` | 16 || || Total number of CPU cores for all database hosts per cloud `mdb.cpu.count` | 64 || || Total virtual memory for all database hosts per cloud `mdb.memory.size` | 512 GB || || Total storage capacity for all clusters per cloud `mdb.ssd.size` | 4,096 GB || || Number of GPUs `mdb.gpu.count` | 0 || |# #### Limits {#mmy-limits} | Type of limit | Minimum value | Maximum value | |:------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------------------------------------------------------------|:-----------------------------------------------------| | Host class | b1.medium (2 × [50%](../../../compute/concepts/performance-levels.md) vCPUs, Intel Broadwell, 4 GB RAM) | m4a-c224-m1792 (224 vCPU, AMD Zen 4, 1,792 GB RAM) | | Number of hosts per cluster configured with either HDD/SSD network storage or an ultra high-speed SSD network storage with three replicas | 1 | 7 | | Number of hosts per cluster configured with either non-replicated or local SSD storage | 3 | 7 | | Amount of data per host with SSD network storage | 10 GB | 6,144 GB | | Amount of data per host with HDD network storage | 10 GB | 2,048 GB | | Amount of data per host when using a non-replicated SSD storage or an ultra high-speed network SSD storage with three replicas | 93 GB | 8,184 GB | | Amount of data per host when using a local SSD storage (for Intel Broadwell and Intel Cascade Lake) | 100 GB | 1,500 GB | | Amount of data per host when using a local SSD storage (for Intel Ice Lake and AMD Zen 4) | 368 GB | 5888 GB | ### Yandex Managed Service for PostgreSQL {#mpg} #### Quotas {#mpg-quotas} #| || Type of limit | Value || || Number of clusters per cloud `mdb.clusters.count` | 16 || || Total number of CPU cores for all database hosts per cloud `mdb.cpu.count` | 64 || || Total virtual memory for all database hosts per cloud `mdb.memory.size` | 512 GB || || Total storage capacity for all clusters per cloud `mdb.ssd.size` | 4,096 GB || || Number of GPUs `mdb.gpu.count` | 0 || |# #### Limits {#mpg-limits} | Type of limit | Minimum value | Maximum value | |:------------------------------------------------------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------------|:-------------------------------------------------| | Host class | b1.medium (2 × [50%](../../../compute/concepts/performance-levels.md) vCPU Intel Broadwell, 4 GB RAM) | m4a-c224-m1792 (224 vCPUs, AMD Zen 4, 1,792 GB RAM) | | Number of hosts per cluster configured with either HDD/SSD network storage or an ultra high-speed SSD network storage with three replicas | 1 | 16 | | Number of hosts per cluster configured with either non-replicated or local SSD storage | 3 | 16 | | Data volume per host with SSD network storage | 10 GB | 8,192 GB | | Amount of data per host when using a network HDD storage (for Intel Broadwell) | 10 GB | 2,048 GB | | Amount of data per host when using a non-replicated SSD storage or an ultra high-speed network SSD storage with three replicas (for AMD Zen 4) | 93 GB | 16,368 GB | | Amount of data per host when using a local SSD storage (for Intel Broadwell and Intel Cascade Lake) | 100 GB | 1,500 GB | | Amount of data per host when using a local SSD storage (for Intel Ice Lake and AMD Zen 4) | 368 GB | 5888 GB | | Connections per user | 1 | 15,985 | | Number of databases per cluster | 1 | 1000 | ### Yandex Managed Service for Valkey™ {#mrd} #### Quotas {#mrd-quotas} #| || **Type of limit** | **Value** || || Number of clusters per cloud `mdb.clusters.count` | 16 || || Total number of CPU cores for all database hosts per cloud `mdb.cpu.count` | 64 || || Total virtual memory for all database hosts per cloud `mdb.memory.size` | 512 GB || || Total storage capacity for all clusters per cloud `mdb.ssd.size` | 4,096 GB || || Number of GPUs `mdb.gpu.count` | 0 || |# #### Limits {#mrd-limits} #| || **Type of limit** | **Minimum value** | **Maximum value** || || Host class | b2.medium (`burstable`, 4 GB RAM) | m4a-c224-m1792 (224 vCPUs, AMD Zen 4, 1,792 GB RAM) || || Number of hosts per unsharded cluster | 1 or 3 depending on the [disk type](../../../managed-valkey/concepts/storage.md#storage-type-selection) | 7 || || Number of shards per sharded cluster | 1 | 10 || || Number of hosts per shard when using a network SSD storage or an ultra high-speed network SSD storage with three replicas | 1 | 7 || || Number of hosts per shard when using a local SSD storage^*^ | 2 | 7 || || Number of hosts per shard when using a non-replicated SSD storage^*^ | 3 | 7 || || Number of hosts per sharded cluster | 1, 2, or 3 hosts depending on the [disk type](../../../managed-valkey/concepts/storage.md#storage-type-selection) | 70 (10 shards × 7 hosts) || || Amount of data per host when using an SSD network storage | Twice the selected amount of RAM | 4,096 GB || || Amount of data per host when using a non-replicated SSD storage^*^ or an ultra high-speed network SSD storage with three replicas | Twice the selected amount of RAM but at least 93 GB | 8,184 GB || || Amount of data per host when using a local SSD storage (for Intel Broadwell and Intel Cascade Lake) | Twice the selected amount of RAM but at least 100 GB | 1,536 GB || || Amount of data per host when using a local SSD storage (for Intel Ice Lake and AMD Zen 4) | Twice the selected amount of RAM but at least 368 GB | 5888 GB || || Number of cluster connections | — | 65,000 || |# ^*^ Read more on how platform selection affects [available storage types](../../../managed-valkey/concepts/storage.md). ### Yandex Message Queue {#mq} #### Quotas {#ymq-quotas} ##### Messages {#ymq-quotas-messages} #| || Type of limitation | Value || || Number of `SendMessage` and `SendMessageBatch` calls per queue | 300 calls per second for a standard queue || || Number of `ReceiveMessage` calls per queue | 300 calls per second for a standard queue || || Number of `DeleteMessage` and `DeleteMessageBatch` calls per queue | 300 calls per second for a standard queue || || Number of `ChangeMessageVisibility` and `ChangeMessageVisibilityBatch` calls per queue | 300 calls per second for a standard queue || || Number of `CreateQueue` calls per cloud | 2 calls per second || || Number of `DeleteQueue` calls per cloud | 5 calls per second || || Number of other request calls per cloud | 100 calls per second || || Number of queues per cloud | 1,000 || |# #### Limits {#ymq-limits} ##### Queues {#ymq-limits-queues} Type of limitation | Value ----- | ----- Minimum delay when enqueuing a message (`DelaySeconds` parameter) | 0 seconds Maximum delay when enqueuing a message (`DelaySeconds` parameter) | 900 seconds (15 minutes) Number of messages being processed per standard queue | 120,000 Number of messages being processed per FIFO queue | 20,000 Rate of enqueueing messages in a FIFO queue | 100 messages per second Queue name | Maximum of 80 characters, including numbers, lowercase and uppercase Latin letters, hyphens, and underscores. The name of a FIFO queue must end with the `.fifo` suffix. ##### Messages {#ymq-limits-messages} Type of limitation | Value ----- | ----- Number of `SendMessage` and `SendMessageBatch` calls per queue | 30 calls per second for a FIFO queue Number of `ReceiveMessage` calls per queue | 30 calls per second for a FIFO queue Number of `DeleteMessage` and `DeleteMessageBatch` calls per queue | 30 calls per second for a FIFO queue Number of `ChangeMessageVisibility` and `ChangeMessageVisibilityBatch` calls per queue | 30 calls per second for a FIFO queue Batch entry ID | Maximum of 80 characters, including numbers, lowercase and uppercase Latin letters, hyphens, and underscores. Maximum number of message attributes | 10 Maximum number of entries per batch | 10 Message content | XML, JSON, and unformatted text. The following Unicode characters are supported: Maximum period for retaining messages in a queue | 1,209,600 seconds (14 days) Minimum period for retaining messages in a queue | 60 seconds (1 minute) Maximum delay when enqueuing a message (`DelaySeconds` parameter) | 900 seconds (15 minutes) Minimum delay when enqueuing a message (`DelaySeconds` parameter) | 0 seconds Maximum message size | 262,144 bytes (256 KB) Minimum message size | 1 byte Maximum message visibility timeout | 12 hours Minimum message visibility timeout | 0 seconds Maximum client message [wait time](../../../message-queue/concepts/long-polling.md) in an empty queue (`WaitTimeSeconds` parameter) | 20 seconds | _ClickHouse® is a registered trademark of [ClickHouse, Inc](https://clickhouse.com)._