This topic lists the ApsaraDB for Redis instances that are phased out. If you have already purchased one or more of these instances, you can continue to use them. The following table shows the maximum number of concurrent connections to each instance, maximum bandwidth, and QPS reference value for these instances.

Standard zone-disaster recovery instances of Community Edition

Instance type InstanceClass (API operation) Maximum number of new connections per second Maximum number of concurrent connections Bandwidth (MB/s) QPS reference value
1 GB zone-disaster recovery instance redis.logic.sharding.drredissdb1g.1db.0rodb.4proxy.default 10000 10000 10 80000
2 GB zone-disaster recovery instance redis.logic.sharding.drredissdb2g.1db.0rodb.4proxy.default 10000 10000 16 80000
4 GB zone-disaster recovery instance redis.logic.sharding.drredissdb4g.1db.0rodb.4proxy.default 10000 10000 24 80000
8 GB zone-disaster recovery instance redis.logic.sharding.drredissdb8g.1db.0rodb.4proxy.default 10000 10000 24 80000
16 GB zone-disaster recovery instance redis.logic.sharding.drredissdb16g.1db.0rodb.4proxy.default 10000 10000 32 80000
32 GB zone-disaster recovery instance redis.logic.sharding.drredissdb32g.1db.0rodb.4proxy.default 10000 10000 32 80000
64 GB zone-disaster recovery instance redis.logic.sharding.drredissdb64g.1db.0rodb.4proxy.default 10000 10000 48 80000

Master-replica cluster instance of Community Edition

Instance type InstanceClass (API operation) Number of shards Maximum number of new connections per second Maximum number of concurrent connections Bandwidth (MB/s) QPS reference value
16 GB cluster instance redis.sharding.small.default 8 50000 80000 768 640000
32 GB cluster instance redis.sharding.mid.default 8 50000 80000 768 640000
64 GB cluster instance redis.sharding.large.default 8 50000 80000 768 640000
128 GB cluster instance redis.sharding.2xlarge.default 16 50000 160000 1536 1280000
256 GB cluster instance redis.sharding.4xlarge.default 16 50000 160000 1536 1280000
512 GB cluster instance redis.sharding.8xlarge.default 32 50000 320000 2048 2560000

Zone-disaster recovery cluster instances of Community Edition

Instance type InstanceClass (API operation) Number of shards Maximum number of new connections per second Maximum number of concurrent connections Bandwidth (MB/s) QPS reference value
16 GB zone-disaster recovery cluster instance redis.logic.sharding.drredismdb16g.8db.0rodb.8proxy.default 8 50000 80000 768 640000
32 GB zone-disaster recovery cluster instance redis.logic.sharding.drredismdb32g.8db.0rodb.8proxy.default 8 50000 80000 768 640000
64 GB zone-disaster recovery cluster instance redis.logic.sharding.drredismdb64g.8db.0rodb.8proxy.default 8 50000 80000 768 640000
128 GB zone-disaster recovery cluster instance redis.logic.sharding.drredismdb128g.16db.0rodb.16proxy.default 16 50000 160000 1536 1280000
256 GB zone-disaster recovery cluster instance redis.logic.sharding.drredismdb256g.16db.0rodb.16proxy.default 16 50000 160000 1536 1280000
512 GB zone-disaster recovery cluster instance redis.logic.sharding.drredismdb512g.32db.0rodb.32proxy.default 32 50000 320000 2048 2560000

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.

FAQ

  • Q: Zone-disaster recovery instances of ApsaraDB for Redis are phased out. How can I create a zone-disaster recovery instance when I use ApsaraDB for Redis?
  • A: Zone-disaster recovery instances of ApsaraDB for Redis are phased out. To use the zone-disaster recovery feature, you can select a zone that supports zone-disaster recovery when you create an ApsaraDB for Redis instance.Zone