Redis 4.0 and 5.0 Instance Specifications¶
This section describes DCS Redis 4.0 and 5.0 instance specifications, including the total memory, available memory, maximum number of connections allowed, maximum/assured bandwidth, and reference performance.
The following metrics are related to the instance specifications:
Used memory: You can check the memory usage of an instance by viewing the Memory Usage and Used Memory metrics.
Maximum connections: The maximum number of connections allowed is the maximum number of clients that can be connected to an instance. To check the number of connections to an instance, view the Connected Clients metric. After an instance is created, you can change the maximum number of connections of the instance by modifying the maxclients parameter on the Instance Configuration > Parameters page on the console.
QPS represents queries per second, which is the number of commands processed per second.
Bandwidth: You can view the Flow Control Times metric to check whether the bandwidth has exceeded the limit.
You can also check the Bandwidth Usage metric. This metric is for reference only, because it may be higher than 100%. For details, see Why Does Bandwidth Usage Exceed 100%?
Note
DCS Redis 4.0 and 5.0 instances are available in single-node, master/standby, and Redis Cluster types.
Only the x86 architecture is supported. The Arm architecture is not supported.
Single-Node Instances¶
Total Memory (GB) | Available Memory (GB) | Max. Connections (Default/Limit) (Count) | Assured/Maximum Bandwidth (Mbit/s) | Reference Performance (QPS) | Specification Code (spec_code in the API) |
|---|---|---|---|---|---|
0.125 | 0.125 | 10,000/10,000 | 40/40 | 80,000 | redis.single.xu1.tiny.128 |
0.25 | 0.25 | 10,000/10,000 | 80/80 | 80,000 | redis.single.xu1.tiny.256 |
0.5 | 0.5 | 10,000/10,000 | 80/80 | 80,000 | redis.single.xu1.tiny.512 |
1 | 1 | 10,000/50,000 | 80/80 | 80,000 | redis.single.xu1.large.1 |
2 | 2 | 10,000/50,000 | 128/128 | 80,000 | redis.single.xu1.large.2 |
4 | 4 | 10,000/50,000 | 192/192 | 80,000 | redis.single.xu1.large.4 |
8 | 8 | 10,000/50,000 | 192/192 | 100,000 | redis.single.xu1.large.8 |
16 | 16 | 10,000/50,000 | 256/256 | 100,000 | redis.single.xu1.large.16 |
24 | 24 | 10,000/50,000 | 256/256 | 100,000 | redis.single.xu1.large.24 |
32 | 32 | 10,000/50,000 | 256/256 | 100,000 | redis.single.xu1.large.32 |
48 | 48 | 10,000/50,000 | 256/256 | 100,000 | redis.single.xu1.large.48 |
64 | 64 | 10,000/50,000 | 384/384 | 100,000 | redis.single.xu1.large.64 |
Master/Standby Instances¶
By default, a master/standby instance has two replicas (including the master). There is one master node.
Number of IP addresses occupied by a master/standby instance = Number of master nodes x Number of replicas. For example:
2 replicas: Number of occupied IP addresses = 1 x 2 = 2
3 replicas: Number of occupied IP addresses = 1 x 3 = 3
The following table lists the specification codes (spec_code) when there are two default replicas. Change the replica quantity in the specification codes based on the actual number of replicas. For example, if an 8 GB master/standby x86-based instance has two replicas, its specification code is redis.ha.xu1.large. r2.8. If it has three replicas, its specification code is redis.ha.xu1.large. r3.8.
Total Memory (GB) | Available Memory (GB) | Max. Connections (Default/Limit) (Count) | Assured/Maximum Bandwidth (Mbit/s) | Reference Performance (QPS) | Specification Code (spec_code in the API) |
|---|---|---|---|---|---|
0.125 | 0.125 | 10,000/10,000 | 40/40 | 80,000 | redis.ha.xu1.tiny.r2.128 |
0.25 | 0.25 | 10,000/10,000 | 80/80 | 80,000 | redis.ha.xu1.tiny.r2.256 |
0.5 | 0.5 | 10,000/10,000 | 80/80 | 80,000 | redis.ha.xu1.tiny.r2.512 |
1 | 1 | 10,000/50,000 | 80/80 | 80,000 | redis.ha.xu1.large.r2.1 |
2 | 2 | 10,000/50,000 | 128/128 | 80,000 | redis.ha.xu1.large.r2.2 |
4 | 4 | 10,000/50,000 | 192/192 | 80,000 | redis.ha.xu1.large.r2.4 |
8 | 8 | 10,000/50,000 | 192/192 | 100,000 | redis.ha.xu1.large.r2.8 |
16 | 16 | 10,000/50,000 | 256/256 | 100,000 | redis.ha.xu1.large.r2.16 |
24 | 24 | 10,000/50,000 | 256/256 | 100,000 | redis.ha.xu1.large.r2.24 |
32 | 32 | 10,000/50,000 | 256/256 | 100,000 | redis.ha.xu1.large.r2.32 |
48 | 48 | 10,000/50,000 | 256/256 | 100,000 | redis.ha.xu1.large.r2.48 |
64 | 64 | 10,000/50,000 | 384/384 | 100,000 | redis.ha.xu1.large.r2.64 |
Redis Cluster Instances¶
In addition to larger memory, Redis Cluster instances feature more connections allowed, higher bandwidth allowed, and more QPS than single-node and master/standby instances.
The following table lists the x86 specification codes (spec_code) when there are two default replicas. Change the replica quantity in the specification codes based on the actual number of replicas. For example, if an 8 GB x86-based instance has two replicas, its specification code is redis.cluster.xu1.large.r2.8. If it has three replicas, its specification code is redis.cluster.xu1.large.r3.8.
IP addresses: Number of occupied IP addresses = Number of shards x Number of replicas. For example:
4 GB | Redis Cluster | 3 replicas: Number of occupied IP addresses = 3 x 3 = 9
Available memory per node = Instance available memory/Master node quantity. For example:
For example, a 64 GB instance has 64 GB available memory and 8 master nodes. The available memory per node is 64/8 = 8 GB.
Maximum connections limit per node = Maximum connections limit/Master node quantity For example:
For example, a 4 GB instance has 3 master nodes and the maximum connections limit is 150,000. The maximum connections limit per node = 150,000/3 = 50,000.
Specification (GB) | Available Memory (GB) | Shards (Master Nodes) | Max. Connections (Default/Limit) (Count) | Assured/Maximum Bandwidth (Mbit/s) | Reference Performance (QPS) | Specification Code (spec_code in the API) |
|---|---|---|---|---|---|---|
4 | 4 | 3 | 30,000 /150,000 | 2304/2304 | 240,000 | redis.cluster.xu1.large.r2.4 |
8 | 8 | 3 | 30,000 /150,000 | 2304/2304 | 240,000 | redis.cluster.xu1.large.r2.8 |
16 | 16 | 3 | 30,000 /150,000 | 2304/2304 | 240,000 | redis.cluster.xu1.large.r2.16 |
24 | 24 | 3 | 30,000 /150,000 | 2304/2304 | 300,000 | redis.cluster.xu1.large.r2.24 |
32 | 32 | 3 | 30,000 /150,000 | 2304/2304 | 300,000 | redis.cluster.xu1.large.r2.32 |
48 | 48 | 6 | 60,000 /300,000 | 4608/4608 | > 300,000 | redis.cluster.xu1.large.r2.48 |
64 | 64 | 8 | 80,000 /400,000 | 6144/6144 | 500,000 | redis.cluster.xu1.large.r2.64 |
96 | 96 | 12 | 120,000 /600,000 | 9216/9216 | > 500,000 | redis.cluster.xu1.large.r2.96 |
128 | 128 | 16 | 160,000 /800,000 | 12,288/12,288 | 1,000,000 | redis.cluster.xu1.large.r2.128 |
192 | 192 | 24 | 240,000 /1,200,000 | 18,432/18,432 | > 1,000,000 | redis.cluster.xu1.large.r2.192 |
256 | 256 | 32 | 320,000 /1,600,000 | 24,576/24,576 | > 2,000,000 | redis.cluster.xu1.large.r2.256 |
384 | 384 | 48 | 480,000 /2,400,000 | 36,864/36,864 | > 2,000,000 | redis.cluster.xu1.large.r2.384 |
512 | 512 | 64 | 640,000 /3,200,000 | 49,152/49,152 | > 2,000,000 | redis.cluster.xu1.large.r2.512 |
768 | 768 | 96 | 960,000 /4,800,000 | 73,728/73,728 | > 2,000,000 | redis.cluster.xu1.large.r2.768 |
1024 | 1024 | 128 | 1,280,000 /6,400,000 | 98,304/98,304 | > 2,000,000 | redis.cluster.xu1.large.r2.1024 |