This topic describes the ApsaraDB for Redis instances that are phased out. If you have purchased these instances, you can continue to use them. The following table lists the maximum number of connections to each instance, maximum bandwidth, and QPS reference value for these instances.
Standard zone-disaster recovery instances of Community Edition
| Instance type | InstanceClass (used in API) | Maximum number of new connections per second | Maximum number of 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 instances of Community Edition
| 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 |
|---|---|---|---|---|---|---|
| 1 GB cluster instance (2 shards) | redis.logic.sharding.512m.2db.0rodb.4proxy.default | 2 | 20000 | 20000 | 48 | 200000 |
| 1 GB cluster instance (4 shards) | redis.logic.sharding.256m.4db.0rodb.4proxy.default | 4 | 40000 | 40000 | 96 | 400000 |
| 2 GB cluster instance (4 shards) | redis.logic.sharding.512m.4db.0rodb.4proxy.default | 4 | 40000 | 40000 | 96 | 400000 |
| 2 GB cluster instance (8 shards) | redis.logic.sharding.256m.8db.0rodb.8proxy.default | 8 | 50000 | 80000 | 192 | 800000 |
| 4 GB cluster instance (8 shards) | redis.logic.sharding.512m.8db.0rodb.8proxy.default | 8 | 50000 | 80000 | 192 | 800000 |
| 4 GB cluster instance (16 shards) | redis.logic.sharding.256m.16db.0rodb.16proxy.default | 16 | 50000 | 160000 | 384 | 1600000 |
| 8 GB cluster instance (16 shards) | redis.logic.sharding.512m.16db.0rodb.16proxy.default | 16 | 50000 | 160000 | 384 | 1600000 |
| 8 GB cluster instance (32 shards) | redis.logic.sharding.256m.32db.0rodb.32proxy.default | 32 | 50000 | 320000 | 768 | 3200000 |
| 16 GB cluster instance (32 shards) | redis.logic.sharding.512m.32db.0rodb.32proxy.default | 32 | 50000 | 320000 | 768 | 3200000 |
| 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 (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 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 |
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.
FAQ
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?
Zone-disaster recovery instances of ApsaraDB for Redis are upgraded. 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.