All Products
Search
Document Center

ApsaraDB for Redis:Standard master-replica instances

Last Updated:Feb 23, 2024

This topic describes the specifications of standard master-replica instances of ApsaraDB for Redis Community Edition. These specifications include the memory capacity, maximum number of connections, maximum bandwidth, and queries per second (QPS) reference value.

Instance specifications

Specification

InstanceClass value (used in API operations)

Number of CPU cores

Maximum number of new connections per second

Maximum number of connections

Bandwidth (Mbit/s)

QPS reference value

256 MB master-replica

redis.master.micro.default

2

10,000

10,000

10

80,000

1 GB master-replica

redis.master.small.default

2

10,000

10,000

10

80,000

2 GB master-replica

redis.master.mid.default

2

10,000

10,000

16

80,000

4 GB master-replica

redis.master.stand.default

2

10,000

10,000

24

80,000

8 GB master-replica

redis.master.large.default

2

10,000

10,000

24

80,000

16 GB master-replica

redis.master.2xlarge.default

2

10,000

10,000

32

80,000

32 GB master-replica

redis.master.4xlarge.default

2

10,000

10,000

32

80,000

64 GB master-replica

redis.master.8xlarge.default

2

10,000

10,000

48

80,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, which 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 Mbit/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 is applicable 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 Mbit/s.

    Note

    If your instance may experience an unexpected or anticipated surge in traffic, you can adjust the bandwidth of the instance on demand. For more information, see Manually increase the bandwidth of an instance.

  • The bandwidth value in the preceding table is the internal bandwidth of the ApsaraDB for Redis instance. The public bandwidth of an instance is determined by the internal bandwidth and is limited by the bandwidth of the connection between the instance and the client. To maximize performance, we recommend that you connect to the instance over an internal network.

Calculation rules for connections

The maximum number of new connections per second refers to the maximum 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

  • Why is the actual bandwidth of my instance different from the bandwidth described in this topic?

    The bandwidths of specific instance types may be adjusted after the service is upgraded. If the actual bandwidth of your instance is different from that described in this topic, you can change the configurations of your instance by selecting the same instance type to update the bandwidth. The price for your instance remains unchanged after the configuration change. For more information, see Change the configurations of an instance.

  • How do I create an instance with 256 MB of memory?

    On the instance buy page, set Billing Method to Subscription and select an instance type with 256 MB of memory.