This topic describes the specifications of performance-enhanced cluster instances of ApsaraDB for Redis Enhanced Edition. These specifications include the memory capacity, number of concurrent connections to each instance, bandwidth, and queries per second (QPS) reference value.
|Instance type||InstanceClass (used in API operations)||Number of I/O threads||Number of shards||Number of proxy servers||Maximum number of new connections per second||Maximum number of concurrent connections||Bandwidth (MB/s)||QPS reference value|
|4 GB performance-enhanced cluster instance||redis.amber.logic.sharding.2g.2db.0rodb.6proxy.multithread||4||2||4||40,000||60,000||192||480,000|
|8 GB performance-enhanced cluster instance||redis.amber.logic.sharding.2g.4db.0rodb.12proxy.multithread||4||4||4||40,000||120,000||384||960,000|
|16 GB performance-enhanced cluster instance||redis.amber.logic.sharding.2g.8db.0rodb.24proxy.multithread||4||8||8||50,000||240,000||768||1,920,000|
|32 GB performance-enhanced cluster instance||redis.amber.logic.sharding.4g.8db.0rodb.24proxy.multithread||4||8||8||50,000||240,000||768||1,920,000|
|64 GB performance-enhanced cluster instance||redis.amber.logic.sharding.8g.8db.0rodb.24proxy.multithread||4||8||8||50,000||240,000||768||1,920,000|
|128 GB performance-enhanced cluster instance||redis.amber.logic.sharding.8g.16db.0rodb.48proxy.multithread||4||16||16||50,000||480,000||1,536||3,840,000|
|256 GB performance-enhanced cluster instance||redis.amber.logic.sharding.16g.16db.0rodb.48proxy.multithread||4||16||16||50,000||480,000||1,536||3,840,000|
|512 GB performance-enhanced cluster instance||redis.amber.logic.sharding.16g.32db.0rodb.96proxy.multithread||4||32||32||50,000||500,000||2,048||7,680,000|
|1,024 GB performance-enhanced cluster instance||redis.amber.logic.sharding.16g.64db.0rodb.192proxy.multithread||4||64||64||50,000||500,000||2,048||15,360,000|
|2,048 GB performance-enhanced cluster instance||redis.amber.logic.sharding.16g.128db.0rodb.384proxy.multithread||4||128||128||50,000||500,000||2,048||30,720,000|
|4,096 GB performance-enhanced cluster instance||redis.amber.logic.sharding.16g.256db.0rodb.768proxy.multithread||4||256||256||50,000||500,000||2,048||61,440,000|
Bandwidth calculation rules
- If network resources are sufficient, Apsaradb for Redis instances do not have bandwidth limits. However, if network resources are insufficient, the limits in the above table take effect.
- The bandwidth value in the table represents the bandwidth of the instance, that is, the total bandwidth of all shards or nodes in the instance.
- The maximum bandwidth of an instance (including all shards or nodes) is 2,048 MB. Bandwidth does not increase even if the number of shards or nodes increases.
- The bandwidth applies to the upstream bandwidth and the 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 in the table is the internal bandwidth of the Redis instance. The Internet bandwidth is determined by the internal bandwidth and is limited by the bandwidth of the connection between the Redis instance and the client. We recommend that you connect to the instance over an internal network to maximize its performance.
Connection number calculation rules
- The following example explains the maximum number of new connections per second: If the maximum number of new connections per second of an instance is 10000, the actual number of concurrent connections at the Nth second after the instance starts to run is 12000, at the (N+1)th second, the actual number of concurrent connections is 22000, then the number of new connections within that second is 22000-12000=10000, which is not greater than the maximum number of new connections per second.
- The maximum number of new connections per second and the maximum number of concorrent connections are the sum of the corresponding values of all shards or nodes in the instance. After 500000 is reached, the maximum number of concorrent connections is not increased even if the number of shards or nodes is increased.
Q: Why does the maximum number of concurrent connections of my instance differ from that of the same instance described in this topic?
A: The maximum number of concurrent connections of some instance types may be adjusted after service upgrades. If the maximum number of concurrent connections of your instance is different than those described in this topic, refer to Modify instance configurations and modify your instance configurations. You are not charged for the same instance type.