This topic describes the specifications of standard master-replica cluster instances of ApsaraDB for Redis Community Edition. These specifications include the memory capacity, the maximum number of connections to each instance, maximum internal bandwidth, and queries per second (QPS) reference value.
|Instance type||InstanceClass (used in API)||Maximum number of new connections per second||Maximum number of connections||Bandwidth (MB/s)||QPS reference value|
|256 MB master-replica instance||redis.master.micro.default||10000||10000||10||80000|
|1 GB master-replica instance||redis.master.small.default||10000||10000||10||80000|
|2 GB master-replica instance||redis.master.mid.default||10000||10000||16||80000|
|4 GB master-replica instance||redis.master.stand.default||10000||10000||24||80000|
|8 GB master-replica instance||redis.master.large.default||10000||10000||24||80000|
|16 GB master-replica instance||redis.master.2xlarge.default||10000||10000||32||80000|
|32 GB master-replica instance||redis.master.4xlarge.default||10000||10000||32||80000|
|64 GB master-replica instance||redis.master.8xlarge.default||10000||10000||48||80000|
Calculation rules for bandwidth
- If network resources are sufficient, the bandwidth is unlimited. However, if network resources are insufficient, the limit on maximum internal bandwidth takes effect.
- The bandwidth value in the table refers to the bandwidth of the instance. It is the sum of bandwidth of all shards or nodes on the instance.
- The upper limit of total bandwidth for a cluster or read/write splitting instance (as shown in the table) is 2,048 MB/s. After the upper limit is reached, the bandwidth cannot be increased even if the number of shards or nodes is increased.
- The bandwidth applies to the upstream bandwidth and downstream bandwidth respectively. If the bandwidth of an instance is 10 MB/s, the upstream and downstream bandwidth of the instance are both 10 MB/s.
- The bandwidth listed in the table is the internal bandwidth of the ApsaraDB for Redis instance. The Internet bandwidth is determined by the internal bandwidth and is limited by the bandwidth of the connection between the instance and a client. We recommend that you connect to the instance over an internal network to maximize the performance.
Calculation rules for connections
- The following example explains the maximum number of new connections that can be added per second: The maximum number of new connections per second of an instance is 10,000. The maximum number of connections is 50,000. The actual number of connections at the Nth second after the instance starts to run is 12,000. Then, at the (N+1)th second, the number of connections is 22,000 (12,000 + 10,000).
- The maximum number of new connections per second and the maximum number of connections are the sum of the corresponding values of all shards or nodes on the instance. After 500,000 is reached, the maximum number of connections cannot be increased even if the number of shards or nodes is increased.
- Why is the actual bandwidth of my instance different from the bandwidth described
in this topic?
The bandwidth of some instance types may be adjusted after the upgrades are complete. If the bandwidth of your instance is different from that described in this topic, you can change configurations and select the same specifications as that of your instance to update the bandwidth. You are not charged for the same specifications. For more information, see Change specifications.
- How do I create an instance with 256 MB of memory?
On the Subscription tab of the buy page, you can find this instance type.