This topic describes the specifications of performance-enhanced standard instances of ApsaraDB for Redis Enhanced Edition (Tair). These specifications include the memory capacity, maximum number of connections to each instance, maximum bandwidth, and queries per second (QPS) reference value.

Instance types

Instance type InstanceClass that is used in API operations Number of CPU cores Number of I/O threads Maximum number of new connections per second Maximum number of connections Maximum bandwidth value (MB/s) QPS reference value
1 GB master-replica performance-enhanced instance redis.amber.master.small.multithread 6 4 10,000 30,000 96 240,000
2 GB master-replica performance-enhanced instance redis.amber.master.mid.multithread 6 4 10,000 30,000 96 240,000
4 GB master-replica performance-enhanced instance redis.amber.master.stand.multithread 6 4 10,000 30,000 96 240,000
8 GB master-replica performance-enhanced instance redis.amber.master.large.multithread 6 4 10,000 30,000 96 240,000
16 GB master-replica performance-enhanced instance redis.amber.master.2xlarge.multithread 6 4 10,000 30,000 96 240,000
32 GB master-replica performance-enhanced instance redis.amber.master.4xlarge.multithread 6 4 10,000 30,000 96 240,000
64 GB master-replica performance-enhanced instance redis.amber.master.8xlarge.multithread 6 4 10,000 30,000 96 240,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 table is the bandwidth of the instance. The bandwidth value is the sum of the bandwidth of all shards or nodes in the instance.
  • The upper limit of the total bandwidth for a read/write splitting instance is 2,048 MB/s. After the upper limit is reached, the bandwidth cannot be increased even if you add more shards or nodes to the read/write splitting instance.
  • The bandwidth value applies to the upstream and downstream bandwidths. For example, if the bandwidth of an instance is 10 MB/s, the upstream and downstream bandwidths of the instance are both 10 MB/s.
    Note If your instance has unexpected or scheduled traffic peaks, you can adjust the bandwidth of the instance as needed. For more information, see Adjust the bandwidth of an ApsaraDB for Redis instance.
  • The bandwidth value in the preceding 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 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

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 per second of an instance is 10,000. The maximum number of connections of 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.

FAQ

Q: Why is the maximum number of connections of my instance different from that described in this topic?

A: The maximum number of connections of specific instance types may be adjusted after the service is upgraded. If the maximum number of connections of your instance is different from that described in this topic, change your instance specifications to update the bandwidth. Make sure that you select the same instance type when you change the specifications. For more information, see Change the configurations of an instance.