This topic describes the specifications of standard hybrid-storage instances of ApsaraDB for Redis Enhanced Edition (Tair), such as the memory capacity, maximum number of concurrent connections to each instance, maximum internal bandwidth, and queries per second (QPS) reference value.

Instance specifications

Note The maximum internal bandwidth is applicable to both upstream bandwidth and downstream bandwidth. If network resources are sufficient, the bandwidth is unlimited for ApsaraDB for Redis instances. However, if network resources are insufficient, the limit on maximum internal bandwidth takes effect for the instances.
Instance type InstanceClass (used in API operations) Number of new connections per second Maximum number of concurrent connections Maximum internal bandwidth (MB/s) QPS reference value Description
Master-replica instance with 16 GB memory and 32 GB disk storage redis.amber.master.16g.2x.ext4.default 10,000 50,000 48 40,000 Master-replica hybrid-storage instance
Master-replica instance with 16 GB memory and 64 GB disk storage redis.amber.master.16g.4x.ext4.default 10,000 50,000 48 40,000 Master-replica hybrid-storage instance
Master-replica instance with 16 GB memory and 128 GB disk storage redis.amber.master.16g.8x.ext4.default 10,000 50,000 48 40,000 Master-replica hybrid-storage instance
Master-replica instance with 32 GB memory and 64 GB disk storage redis.amber.master.32g.2x.ext4.default 10,000 50,000 48 40,000 Master-replica hybrid-storage instance
Master-replica instance with 32 GB memory and 128 GB disk storage redis.amber.master.32g.4x.ext4.default 10,000 50,000 48 40,000 Master-replica hybrid-storage instance
Master-replica instance with 32 GB memory and 256 GB disk storage redis.amber.master.32g.8x.ext4.default 10,000 50,000 48 40,000 Master-replica hybrid-storage instance
Master-replica instance with 64 GB memory and 128 GB disk storage redis.amber.master.64g.2x.ext4.default 10,000 50,000 48 40,000 Master-replica hybrid-storage instance
Master-replica instance with 64 GB memory and 256 GB disk storage redis.amber.master.64g.4x.ext4.default 10,000 50,000 48 40,000 Master-replica hybrid-storage instance
Master-replica instance with 64 GB memory and 512 GB disk storage redis.amber.master.64g.8x.ext4.default 10,000 50,000 48 40,000 Master-replica hybrid-storage instance

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.