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 specifications

Instance type InstanceClass (API operation) Number of shards Maximum number of new connections per second Maximum number of concurrent connections Bandwidth (Mbit/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 40000 384 120000
64 GB memory and 512 GB disk storage (4 shards) redis.amber.sharding.16g.4db.0rodb.12proxy.8x.ext4.default 4 40000 40000 384 120000
128 GB memory and 512 GB disk storage (4 shards) redis.amber.sharding.32g.4db.0rodb.12proxy.4x.ext4.default 4 40000 40000 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 40000 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 40000 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 40000 384 120000
128 GB memory and 512 GB disk storage (8 shards) redis.amber.sharding.16g.8db.0rodb.24proxy.4x.ext4.default 8 50000 80000 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 80000 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 80000 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 80000 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 80000 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 80000 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 160000 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 160000 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 160000 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 160000 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 160000 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 160000 1536 480000

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.