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, maximum bandwidth, and queries per second (QPS) reference value for these instances.
Standard zone-disaster recovery instances of Community Edition
Instance type | InstanceClass value (used in API operations) | Maximum number of new connections per second | Maximum number of connections | Maximum 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 value (used in API operations) | Number of shards | Maximum number of new connections per second | Maximum number of connections | Maximum 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 value (used in API operations) | Number of shards | Maximum number of new connections per second | Maximum number of connections | Maximum 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 values
Each bandwidth value in the preceding table represents the maximum bandwidth for an instance of the corresponding instance type, which is the combined bandwidth of all shards or nodes in the instance.
The bandwidth value applies to the upstream and downstream bandwidths. For example, if the bandwidth of an instance is 10 Mbit/s, the upstream and downstream bandwidths of the instance are both 10 Mbit/s.
NoteIf your instance has unexpected or scheduled traffic peaks, you can adjust the bandwidth of the instance. For more information, see Manually increase the bandwidth of an instance.
The bandwidth limits of Tair and Redis Open-Source Edition refer to the data transfer capacity of individual shards within their respective distributed systems. The limits are generally independent of the network connection types used by clients to connect to the shards.
For information about the FAQ about bandwidth, see FAQ about bandwidth.
Calculation rules for connections
The maximum number of new connections per second refers to the upper limit on the number of connections that can be established per second. For example, the maximum number of new connections to an instance per second is 10,000, the maximum allowed number of connections to the instance is 50,000, and the actual number of connections at the Nth second after the instance starts to run is 12,000. In this case, the maximum number of connections at the (N+1)th second is 22,000. This value is calculated by using the following formula: 12,000 + 10,000.
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?