Plans, statuses and limits
The compute plans a key-value store can use and the cache size each gives, the eviction policies, what the statuses mean, and the rules for names and sizes.
Compute plans
A plan fixes the store's CPU request and limit and its memory; the memory request equals the limit, because a cache uses the memory it is given all the time. The cache size limit derived from the memory limit is three quarters of it — the rest is left for the server itself. These are the plans every installation gets; your platform operator may have added more.
| Plan | CPU | Memory | Derived cache size limit | Meant for production |
|---|---|---|---|---|
| nano | 0.1–0.5 | 256 MiB | 192mb |
No |
| small | 0.25–1 | 1 GiB | 768mb |
No |
| medium | 0.5–2 | 4 GiB | 3072mb |
Yes |
| large | 1–4 | 8 GiB | 6144mb |
Yes |
| xlarge | 2–6 | 16 GiB | 12288mb |
Yes |
| 2xlarge | 4–8 | 32 GiB | 24576mb |
Yes |
Every plan runs a single server. A store created without a plan gets 0.1–0.5 CPU and 256 MiB of
memory requested with a 512 MiB limit, which derives a 384mb cache size limit.
Eviction policies
The eviction policy decides what happens when the cache size limit is reached. A store accepts
allkeys-lru, allkeys-lfu, allkeys-random, volatile-lru, volatile-lfu, volatile-random,
volatile-ttl and noeviction — the values of Valkey's own maxmemory-policy setting, which behave
as Valkey defines them.
allkeys-lru, the default, evicts the least recently used key.noevictionevicts nothing: writes return errors instead.
Statuses
| Status | Meaning |
|---|---|
| Creating | The server is not ready, and the store has not been changed since it was created — normally while it starts for the first time. |
| Running | The server is ready and accepts connections. |
| Updating | The server is not ready after the store was changed — normally while it restarts with the change. |
| Stopped | The store has been stopped; it holds nothing. |
| Degraded | The platform hit an error while applying the store. It keeps trying. |
An operation on the Operations tab — a create, a change, a start, a stop or a restart — ends as failed when the store has not settled five minutes after it began, naming the last status the store reported.
Names and formats
| What | Rule |
|---|---|
| Cache name | 3 to 50 characters in the portal, up to 63 through the API: lowercase letters, digits and hyphens, not starting or ending with a hyphen; unique in the resource group; cannot be changed |
| Cache size limit | A number with an optional unit b, kb, k, mb, m, gb or g, in lowercase, such as 512mb or 2gb; empty means derived |
| Allowed CIDR ranges | IPv4 or IPv6 ranges in CIDR notation, separated by commas |
| Replicas | 1 — replication is not available |
| Persistence | Not available — a store keeps no data across a restart |