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 types

Instance type InstanceClass (used in API) Number of I/O threads Number of shards Maximum number of new connections per second Maximum number of connections Bandwidth (MB/s) QPS reference value
4 GB performance-enhanced cluster instance redis.amber.logic.sharding.2g.2db.0rodb.6proxy.multithread 4 2 40000 60000 192 480000
8 GB performance-enhanced cluster instance redis.amber.logic.sharding.2g.4db.0rodb.12proxy.multithread 4 4 40000 120000 384 960000
16 GB performance-enhanced cluster instance redis.amber.logic.sharding.2g.8db.0rodb.24proxy.multithread 4 8 50000 240000 768 1920000
32 GB performance-enhanced cluster instance redis.amber.logic.sharding.4g.8db.0rodb.24proxy.multithread 4 8 50000 240000 768 1920000
64 GB performance-enhanced cluster instance redis.amber.logic.sharding.8g.8db.0rodb.24proxy.multithread 4 8 50000 240000 768 1920000
128 GB performance-enhanced cluster instance redis.amber.logic.sharding.8g.16db.0rodb.48proxy.multithread 4 16 50000 480000 1536 3840000
256 GB performance-enhanced cluster instance redis.amber.logic.sharding.16g.16db.0rodb.48proxy.multithread 4 16 50000 480000 1536 3840000
512 GB performance-enhanced cluster instance redis.amber.logic.sharding.16g.32db.0rodb.96proxy.multithread 4 32 50000 500000 2048 7680000
1,024 GB performance-enhanced cluster instance redis.amber.logic.sharding.16g.64db.0rodb.192proxy.multithread 4 64 50000 500000 2048 15360000
2,048 GB performance-enhanced cluster instance redis.amber.logic.sharding.16g.128db.0rodb.384proxy.multithread 4 128 50000 500000 2048 30720000
4,096 GB performance-enhanced cluster instance redis.amber.logic.sharding.16g.256db.0rodb.768proxy.multithread 4 256 50000 500000 2048 61440000

Calculation rules for bandwidths

  • If network resources are sufficient, the bandwidth is unlimited. However, if network resources are insufficient, the maximum internal bandwidth is limited.
  • The bandwidth value in the table is the bandwidth of the instance. It is the sum of the bandwidth of all shards or nodes on the instance.
  • When the default proxy endpoint is used by a cluster instance, the upper limit of bandwidth for the cluster instance 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.
    Note You can apply for a private endpoint to enable direct connections to a cluster instance. This allows you to handle a large number of connections and improves service performance. For more information, see Enable a direct connection. The following sections show the bandwidth limits after you enable direct connections:
    • Community Edition: 48 MB/s × Number of shards. For example, for a cluster instance of Community Edition with 128 shards, the maximum bandwidth is 6,144 MB/s after direct connections are enabled.
    • Enhanced Edition (Tair): 96 MB/s × number of shards. For example, for a cluster instance of Enhanced Edition with 128 shards, the maximum bandwidth is 12,288 MB/s after direct connections are enabled.
  • The bandwidth separately applies to the upstream bandwidth and downstream bandwidth. 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 depends on the internal bandwidth and is limited by the bandwidth of each 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 shows 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.

FAQ

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 Change specifications and modify your instance configurations. You are not charged for the same instance type.