This document contains the current resource capacity limits and per-minute API request quotas for Memorystore for Valkey.
Instance limits
Memorystore for Valkey enforces the following usage limits:
| Limit | Value |
|---|---|
| Databases per instance | 1 |
| Usage units per instance | 250 |
Max clients
Max clients is the maximum number of client connections that you can have for each node of a node type without experiencing performance issues.
To make sure that you don't exceed the maximum number of client connections, we
recommend that you monitor the /instance/node/clients/connected_clients metric.
The following table lists the node types that are available for Memorystore for Valkey and the maximum number of client connections that you can have for each node type.
| Node type | Max clients1 |
|---|---|
| shared-core-nano | 5,000 |
| standard-small | 16,000 (default). Max value is 32,000 |
| highmem-medium | 32,000 (default). Max value is 64,000 |
| highmem-xlarge | 64,000 |
1 To learn how to adjust the maximum client connection limit, see Configure an instance.
Instance usage units
The per-project instance usage units for a Memorystore for Valkey instance is calculated by the following formula:
Instance usage units = (shard_count) * (1 + replica_count)
The regional quota for Memorystore for Valkey limits the total amount of usage units that you can provision across all of your Memorystore for Valkey instances in a region.
For example, if you provision three instances in your project with 3 shards and
1 replica each in us-central1, you have consumed 18 units out of the total
regional unit quota for us-central1. To request a higher quota for a region,
see Regional instance usage unit quota increases.
Per-minute API requests quota
The per-minute quotas for Memorystore for Valkey API requests/operations are as follows, and are subject to change:
| API Requests Quota | Value |
|---|---|
| Create or delete Valkey instance requests per project per minute | 10 |
| Valkey instance requests per project per minute | 60 |
Create or delete Valkey instance requests include:
- Create operations (
gcloud memorystore instances create) - Delete operations (
gcloud memorystore instances delete)
Memorystore for Valkey API operations include:
- Get operations (
gcloud memorystore instances describe) - List operations (
gcloud memorystore instances list) - Create operations (
gcloud memorystore instances create) - Delete operations (
gcloud memorystore instances delete) - Update operations (
gcloud rmemorystore instances update)
This quota is for memorystore.googleapis.com requests/operations, not OSS Valkey protocol/commands. These limits apply to each Google Cloud console project and are shared across all applications and IP addresses using that project.