This topic describes the specifications of master-replica cluster instances of ApsaraDB for Redis Community Edition. These specifications include the memory capacity, number of concurrent connections to each instance, maximum internal bandwidth, and queries per second (QPS) reference value.

Instance types

Instance type InstanceClass (used in API) Number of shards Maximum number of new connections per second Maximum number of connections Bandwidth (MB/s) QPS reference value
16 GB cluster instance redis.logic.sharding.2g.8db.0rodb.8proxy.default 8 50000 80000 768 640000
32 GB cluster instance redis.logic.sharding.4g.8db.0rodb.8proxy.default 8 50000 80000 768 640000
64 GB cluster instance redis.logic.sharding.8g.8db.0rodb.8proxy.default 8 50000 80000 768 640000
128 GB cluster instance redis.logic.sharding.8g.16db.0rodb.16proxy.default 16 50000 160000 1536 1280000
256 GB cluster instance redis.logic.sharding.16g.16db.0rodb.16proxy.default 16 50000 160000 1536 1280000
512 GB cluster instance redis.logic.sharding.16g.32db.0rodb.32proxy.default 32 50000 320000 2048 2560000

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

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 they are upgraded. 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.