Product limits
Familiarize yourself with these limitations before you start building your EdgeKV data model.
EdgeKV is only supported in EdgeWorker IDs created using the Dynamic Compute resource tier. Refer to the resource tiers section in the EdgeWorkers User Guide for more information.
| Description | Limit |
|---|---|
| Number of namespaces per account on each network | 20 on the staging network 20 on the production network Note: The "default" namespace, created automatically on each network, counts towards this limit. |
| Namespace retention | Data within the "default" namespace is stored for 6 months after it was written or last updated. You cannot modify the retention period for the "default" namespace. For all other namespaces that you create, you must specify a retention period upon creation. You can also update the retention period for any existing namespace other than the "default" namespace. For more information refer to Update namespace details in the EdgeKV API documentation. You should only use the default namespace for experimentation and testing purposes. When deploying your EdgeKV database in production, please use a new namespace with a different name. |
| Namespace retention for data written to a Sandbox environment | Data written to a sandbox environment has a 2 day retention period regardless of the retention period of the namespace in which the data exists. |
| Data storage per account | 20 TB (recommended limit) Writes to the EdgeKV database will fail after 21 TB. Note: 1 TB = 1,000,000,000,000 Bytes |
| Namespace name limitations | 1 to 32 characters in length. Only alphanumeric (0-9, a-z, A-Z), underscore (_), and (-) dash characters are supported. You cannot use the (-) dash character to start the name. |
| Items per account/namespace | 200,000,000 per customer account 10,000,000 per namespace Note: If these limits are exceeded writes will continue to succeed until the database reaches the data storage limit. Exceeding these limits may, however, have a significant impact on the read performance of all data within your database. |
| Items per group | There is no limit to the number of items you can add to a group. There is, as specified above, a limit to the number of items you can create per account/namespace. |
| Group name limitations | 1 to 128 characters in length. Only alphanumeric (0-9, a-z, A-Z), underscore (_), and (-) dash characters are supported. You cannot use the (-) dash character to start the name. |
| Key name limitations | 1 to 512 characters in length. Only alphanumeric (0-9, a-z, A-Z), underscore (_), and (-) dash characters are supported. You cannot use the (-) dash character to start the name. |
| Value size | 999,999 Bytes |
| Number of item reads per second from EdgeWorkers | The maximum number of reads per second is defined by the EdgeWorkers HTTP sub-request limitations. EdgeKV has further limits that apply globally: - An estimated aggregate of 10,000 reads per second from all EdgeWorkers for up to 98/2 read/write ratio. - An aggregate hard limit of 1,000 reads per second from all EdgeWorkers when the write ratio is greater than 2% or for cold hits. Refer to the Throughput FAQ for more details. |
| Number of group reads per second | A group read returns N items up to the items per group limit below. Each of these are counted as a separate request towards the item read limit above. |
| Number of items returned per group read request | 100 by default. You can use the maxItems query string to configure the number of items returned to a value between 1 and 1000. For more information see, List items within a group.If the number of items returned exceeds the default value of 100 or the number specified using the maxItems query string the operation returns a random set of data. |
| Number of item writes/deletes per second from EdgeWorkers | The number of item writes/deletes supported from all EdgeWorkers is: - 200 per second if the item value size is less than 10 KB - 40 per second if the item value size is 10 KB to less than 100 KB - 15 per second if the item value size is 100 KB to less than 250 KB - 1 per second if the item value size is 250 KB to less than 1MB These limits exist to help distribute resources across customers. Note: Exceeding more than an aggregate of 40 write/delete operations per second for distinct items negatively impacts read performance and throughput. |
| Number of Administrative API operations per second | The limits above apply to Administrative API operations but are further restricted as follows: - Burst limit: 24 hits per second (during any 5 second period) - Average limit: 18 hits per second (during any 2 minute period) Note: Exceeding these limits will cause subsequent requests to be blocked. The block lasts 10 minutes after the limit is no longer exceeded. The API response will have a 403 http status code in this case. |
| Number of tokens per account | 50 If you generate more than one token per namespace, you will have redundant tokens that reduce your remaining available tokens. Refer to the Generate and retrieve EdgeKV access tokens section for more information. Expired tokens may count towards the limit for one month after expiry. Please contact us if you encounter this problem. You can list expired tokens using the EdgeKV CLI. Revoked tokens do not count towards this limit. |
| Token name limitations | 1 to 32 characters in length. Only alphanumeric (0-9, a-z, A-Z), (_) underscore, and (-) dash characters are supported. You cannot use the (-) dash character to start the name. |
| Maximum number of namespace permissions per token | 20 |
| Maximum number of EdgeWorker IDs per token | 8 |
| Maximum number of token Administrative API operations per second | Maximum of 1 per second or 10 per minute. |
Updated 3 months ago