This document lists the quotas and limits that apply to AlloyDB for PostgreSQL.
Quotas
A quota restricts how much of a particular shared Google Cloud resource your Cloud project can use, including hardware, software, and network components.
Quotas are part of a system that does the following:
- Monitors your use or consumption of Google Cloud products and services.
- Restricts your consumption of those resources for reasons including ensuring fairness and reducing spikes in usage.
- Maintains configurations that automatically enforce prescribed restrictions.
- Provides a means to make or request changes to the quota.
When a quota is exceeded, in most cases, the system immediately blocks access to the relevant Google resource, and the task that you're trying to perform fails. In most cases, quotas apply to each Cloud project and are shared across all applications and IP addresses that use that Cloud project.
Check your quotas
To check the current quotas for AlloyDB resources in your project, go to the Quotas page in the Google Cloud console and filter for AlloyDB API.
Request a quota increase
To increase or decrease most quotas, use the Google Cloud console. For more information, see Requesting a higher quota.
Limits
There are also limits on AlloyDB resources. These limits are unrelated to the quota system. The limits shown here apply during the preview release period and are subject to increase upon general availability of AlloyDB. To request a limit increase during the preview release period, contact your Google Cloud sales team.
| Item | Limit |
|---|---|
| Clusters per project per region | 3 |
| vCPUs per project per region | 1,100 |
| Read pool nodes per cluster (across all read pool instances) | 20 |
| Database storage per cluster | 500 GB (64 TB at general availability) |
| Maximum concurrent connections per instance | Depends on the machine type of the instance’s VM, as described below in Maximum concurrent connections. |
Maximum concurrent connections
When you create an instance, AlloyDB automatically determines the
maximum concurrent connections for the instance based on the machine type you
specify, and sets the max_connections flag to this value. Google recommends
that you use this automatically-determined value to ensure instance stability.
You can find the maximum concurrent connections value for your instance by connecting to your instance and running this command:
SELECT * FROM pg_settings WHERE name = 'max_connections';
If you change the value of max_connections, the value on a read pool instance
must be greater than or equal to the value on the primary instance.