This topic describes the specifications of hybrid-storage cluster instances of ApsaraDB for Redis Enhanced Edition (Tair). These specifications include the memory and disk capacities, number of connections, maximum bandwidth, and queries per second (QPS) reference value.
Note Hybrid-storage instances are phrased out. For more information, see End-of-Sale for ApsaraDB for Redis hybrid-storage instances. We recommend that you choose Persistent memory-optimized instances.
If you have purchased a hybrid-storage instance, you can submit a ticket to migrate the data of the instance.
Instance types
Instance type | InstanceClass value (used in API operations) | Number of CPU cores | Number of shards | Maximum number of new connections per second | Maximum number of connections ( direct connection mode ) | Maximum number of connections ( proxy mode ) | Maximum 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 | 24 | 4 | 40,000 | 120,000 | 500,000 | 384 | 120,000 |
64 GB memory and 512 GB disk storage (4 shards) | redis.amber.sharding.16g.4db.0rodb.12proxy.8x.ext4.default | 24 | 4 | 40,000 | 120,000 | 500,000 | 384 | 120,000 |
128 GB memory and 512 GB disk storage (4 shards) | redis.amber.sharding.32g.4db.0rodb.12proxy.4x.ext4.default | 24 | 4 | 40,000 | 120,000 | 500,000 | 384 | 120,000 |
128 GB memory and 1,024 GB disk storage (4 shards) | redis.amber.sharding.32g.4db.0rodb.12proxy.8x.ext4.default | 24 | 4 | 40,000 | 120,000 | 500,000 | 384 | 120,000 |
256 GB memory and 1,024 GB disk storage (4 shards) | redis.amber.sharding.64g.4db.0rodb.12proxy.4x.ext4.default | 24 | 4 | 40,000 | 120,000 | 500,000 | 384 | 120,000 |
256 GB memory and 2,048 GB disk storage (4 shards) | redis.amber.sharding.64g.4db.0rodb.12proxy.8x.ext4.default | 24 | 4 | 40,000 | 120,000 | 500,000 | 384 | 120,000 |
128 GB memory and 512 GB disk storage (8 shards) | redis.amber.sharding.16g.8db.0rodb.24proxy.4x.ext4.default | 48 | 8 | 50,000 | 240,000 | 500,000 | 768 | 240,000 |
128 GB memory and 1,024 GB disk storage (8 shards) | redis.amber.sharding.16g.8db.0rodb.24proxy.8x.ext4.default | 48 | 8 | 50,000 | 240,000 | 500,000 | 768 | 240,000 |
256 GB memory and 1,024 GB disk storage (8 shards) | redis.amber.sharding.32g.8db.0rodb.24proxy.4x.ext4.default | 48 | 8 | 50,000 | 240,000 | 500,000 | 768 | 240,000 |
256 GB memory and 2,048 GB disk storage (8 shards) | redis.amber.sharding.32g.8db.0rodb.24proxy.8x.ext4.default | 48 | 8 | 50,000 | 240,000 | 500,000 | 768 | 240,000 |
512 GB memory and 2,048 GB disk storage (8 shards) | redis.amber.sharding.64g.8db.0rodb.24proxy.4x.ext4.default | 48 | 8 | 50,000 | 240,000 | 500,000 | 768 | 240,000 |
512 GB memory and 4,096 GB disk storage (8 shards) | redis.amber.sharding.64g.8db.0rodb.24proxy.8x.ext4.default | 48 | 8 | 50,000 | 240,000 | 500,000 | 768 | 240,000 |
256 GB memory and 1,024 GB disk storage (16 shards) | redis.amber.sharding.16g.16db.0rodb.48proxy.4x.ext4.default | 96 | 16 | 50,000 | 480,000 | 500,000 | 1,536 | 480,000 |
256 GB memory and 2,048 GB disk storage (16 shards) | redis.amber.sharding.16g.16db.0rodb.48proxy.8x.ext4.default | 96 | 16 | 50,000 | 480,000 | 500,000 | 1,536 | 480,000 |
512 GB memory and 2,048 GB disk storage (16 shards) | redis.amber.sharding.32g.16db.0rodb.48proxy.4x.ext4.default | 96 | 16 | 50,000 | 480,000 | 500,000 | 1,536 | 480,000 |
512 GB memory and 4,096 GB disk storage (16 shards) | redis.amber.sharding.32g.16db.0rodb.48proxy.8x.ext4.default | 96 | 16 | 50,000 | 480,000 | 500,000 | 1,536 | 480,000 |
1,024 GB memory and 4,096 GB disk storage (16 shards) | redis.amber.sharding.64g.16db.0rodb.48proxy.4x.ext4.default | 96 | 16 | 50,000 | 480,000 | 500,000 | 1,536 | 480,000 |
1,024 GB memory and 8,192 GB disk storage (16 shards) | redis.amber.sharding.64g.16db.0rodb.48proxy.8x.ext4.default | 96 | 16 | 50,000 | 480,000 | 500,000 | 1536 | 480,000 |
Notes about CPU cores
To ensure service stability, the system reserves a CPU core to process background tasks. In a cluster instance or a read/write splitting instance, the system reserves a CPU core for each data shard or each read replica to process background tasks.
Calculation rules for bandwidth values
- The bandwidth value in the preceding tables is the bandwidth of the instance. The bandwidth value is the sum of the bandwidths of all shards or nodes in the instance. Each shard has the following bandwidth limits:
- Community Edition: If the memory of each shard is less than or equal to 1 GB, the maximum bandwidth of each shard is 48 Mbit/s. If the memory of each shard is greater than 1 GB, the maximum bandwidth of each shard is 96 Mbit/s.
- Enhanced Edition (Tair): The maximum bandwidth of each shard is 96 Mbit/s.
- If the default proxy endpoint is used by a cluster instance, the upper limit of bandwidth for the cluster instance is 2,048 Mbit/s. After the upper limit is reached, the bandwidth cannot be increased even if you add more shards to the cluster instance. To handle network traffic peaks, you can enable the direct connection mode. For more information, see Enable the direct connection mode. The direct connection mode is applicable only to cluster instances. After you enable the direct connection mode, take note of the following items:
- The upper limit of connections is equal to the maximum number of connections for a single shard multiplied by the number of shards. The maximum number of connections for a single shard in Community Edition is 10,000. The maximum number of connections for a single shard in Enhanced Edition (Tair) is 30,000.
- The upper limit of the bandwidth is equal to the maximum bandwidth of a single shard multiplied by the number of shards. For example, if a cluster instance contains 128 shards and each shard is allocated with the memory of more than 1 GB and a maximum bandwidth of 96 Mbit/s, the bandwidth limit of the instance is 12,288 Mbit/s after you enable the direct connection mode.
- 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. Note If your instance has unexpected or scheduled traffic peaks, you can adjust the bandwidth of the instance. For more information, see Adjust the bandwidth of an ApsaraDB for Redis instance.
- The bandwidth value in the preceding tables is the internal bandwidth of the ApsaraDB for Redis instance. The public bandwidth is determined by the internal bandwidth and is limited by the bandwidth of the connection between the ApsaraDB for Redis instance and the client. We recommend that you connect to the instance over an internal network to maximize performance.
Calculation rules for connections
Item | Description |
---|---|
Maximum number of connections |
|
Number of new connections per second | The maximum number of new connections per second refers to the number of connections that are allowed to be established per second. The following example shows how the maximum number of new connections per second affects the maximum number of connections at a specific second: The maximum number of new connections to an instance per second is 10,000. The maximum number of connections to the instance 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 maximum number of connections is 22,000, which is calculated by using the following formula: 12,000 + 10,000. Note If the instance is connected in direct connection mode, connection performance degrades because proxy nodes are bypassed. For more information about the direct connection mode, see Enable the direct connection mode. The maximum number of new connections per second for a single data shard is 2,000. For example, if an instance has four data shards, the maximum number of new connections per second is 8,000. |