[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-19。"],[],[],null,["# Quotas and limits\n\nThis document contains the current resource capacity limits and per-minute API\nrequest quotas for Memorystore for Valkey.\n\nInstance limits\n---------------\n\nMemorystore for Valkey enforces the following usage limits:\n\n### Max clients\n\n*Max clients* is the maximum number of client connections that you can have for\neach node of a node type without experiencing performance issues.\n\nTo make sure that you don't exceed the maximum number of client connections, we\nrecommend that you monitor the [`/instance/node/clients/connected_clients`](/memorystore/docs/valkey/supported-monitoring-metrics#node-level_metrics) metric.\n\nThe following table lists the node types that are available for\nMemorystore for Valkey and the maximum number of client connections that you\ncan have for each node type.\n\n| **Caution** : We recommend that you use the `shared-core-nano` node type for development or testing purposes only. If you run Memorystore for Valkey in a production environment, then we recommend using the `standard-small`, `highmem-medium`, or `highmem-xlarge` node types. For more information about these node types, see [Choose a node type](/memorystore/docs/valkey/instance-node-specification#choose-node-type).\n\n^1^ To learn how to adjust the maximum client connection limit, see\n[Configure an instance](/memorystore/docs/valkey/configure-instances).\n\n### Instance usage units\n\nThe per-project instance usage units for a Memorystore for Valkey instance is\ncalculated by the following formula:\n\nInstance usage units = (shard_count) \\* (1 + replica_count)\n\nThe regional quota for Memorystore for Valkey limits the total amount of usage\nunits that you can provision across all of your Memorystore for Valkey instances\nin a region.\n\nFor example, if you provision three instances in your project with 3 shards and\n1 replica each in `us-central1`, you have consumed 18 units out of the total\nregional unit quota for `us-central1`. To request a higher quota for a region,\nsee [Regional instance usage unit quota increases](/memorystore/docs/valkey/quotas#regional_instance_usage_unit_quota_increases).\n\nPer-minute API requests quota\n-----------------------------\n\n| **Note:**\n| - You cannot request a quota increase for Memorystore for Valkey API operations, such as instance `create`, `update`, and `delete`. There is no limit to the number of Valkey commands you can run, such as Valkey `SET`, `GET`, and `DEL`.\n| - Follow the [Exponential backoff recommendations](/memorystore/docs/valkey/exponential-backoff) to reduce the number of API requests made if an error is encountered.\n\nThe per-minute quotas for Memorystore for Valkey API requests/operations are as follows, and are subject to change:\n\nCreate or delete Valkey instance requests include:\n\n- Create operations (`gcloud memorystore instances create`)\n- Delete operations (`gcloud memorystore instances delete`)\n\nMemorystore for Valkey API operations include:\n\n- Get operations (`gcloud memorystore instances describe`)\n- List operations (`gcloud memorystore instances list`)\n- Create operations (`gcloud memorystore instances create`)\n- Delete operations (`gcloud memorystore instances delete`)\n- Update operations (`gcloud rmemorystore instances update`)\n\nThis quota is for memorystore.googleapis.com requests/operations, not OSS Valkey\nprotocol/commands. These limits apply to each Google Cloud console project and\nare shared across all applications and IP addresses using that project."]]
