This topic describes the specifications of hybrid-storage cluster instances of ApsaraDB for Redis Enhanced Edition (Tair). These specifications include the memory and disk capacity, maximum 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
64 GB memory and 256 GB disk storage (4 shards) redis.amber.sharding.16g.4db.0rodb.12proxy.4x.ext4.default 4 40000 200000 384 120000
64 GB memory and 512 GB disk storage (4 shards) redis.amber.sharding.16g.4db.0rodb.12proxy.8x.ext4.default 4 40000 200000 384 120000
128 GB memory and 512 GB disk storage (4 shards) redis.amber.sharding.32g.4db.0rodb.12proxy.4x.ext4.default 4 40000 200000 384 120000
128 GB memory and 1,024 GB disk storage (4 shards) redis.amber.sharding.32g.4db.0rodb.12proxy.8x.ext4.default 4 40000 200000 384 120000
256 GB memory and 1,024 GB disk storage (4 shards) redis.amber.sharding.64g.4db.0rodb.12proxy.4x.ext4.default 4 40000 200000 384 120000
256 GB memory and 2,048 GB disk storage (4 shards) redis.amber.sharding.64g.4db.0rodb.12proxy.8x.ext4.default 4 40000 200000 384 120000
128 GB memory and 512 GB disk storage (8 shards) redis.amber.sharding.16g.8db.0rodb.24proxy.4x.ext4.default 8 50000 400000 768 240000
128 GB memory and 1,024 GB disk storage (8 shards) redis.amber.sharding.16g.8db.0rodb.24proxy.8x.ext4.default 8 50000 400000 768 240000
256 GB memory and 1,024 GB disk storage (8 shards) redis.amber.sharding.32g.8db.0rodb.24proxy.4x.ext4.default 8 50000 400000 768 240000
256 GB memory and 2,048 GB disk storage (8 shards) redis.amber.sharding.32g.8db.0rodb.24proxy.8x.ext4.default 8 50000 400000 768 240000
512 GB memory and 2,048 GB disk storage (8 shards) redis.amber.sharding.64g.8db.0rodb.24proxy.4x.ext4.default 8 50000 400000 768 240000
512 GB memory and 4,096 GB disk storage (8 shards) redis.amber.sharding.64g.8db.0rodb.24proxy.8x.ext4.default 8 50000 400000 768 240000
256 GB memory and 1,024 GB disk storage (16 shards) redis.amber.sharding.16g.16db.0rodb.48proxy.4x.ext4.default 16 50000 500000 1536 480000
256 GB memory and 2,048 GB disk storage (16 shards) redis.amber.sharding.16g.16db.0rodb.48proxy.8x.ext4.default 16 50000 500000 1536 480000
512 GB memory and 2,048 GB disk storage (16 shards) redis.amber.sharding.32g.16db.0rodb.48proxy.4x.ext4.default 16 50000 500000 1536 480000
512 GB memory and 4,096 GB disk storage (16 shards) redis.amber.sharding.32g.16db.0rodb.48proxy.8x.ext4.default 16 50000 500000 1536 480000
1,024 GB memory and 4,096 GB disk storage (16 shards) redis.amber.sharding.64g.16db.0rodb.48proxy.4x.ext4.default 16 50000 500000 1536 480000
1,024 GB memory and 8,192 GB disk storage (16 shards) redis.amber.sharding.64g.16db.0rodb.48proxy.8x.ext4.default 16 50000 500000 1536 480000

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.