All Products
Search
Document Center

ApsaraDB for Redis:Specifications of ApsaraDB for Redis Community Edition cloud-native instances

Last Updated:Jan 16, 2024

This topic describes the specifications of ApsaraDB for Redis Community Edition cloud-native instances. The specifications include the memory capacity, CPU performance, maximum bandwidth, maximum number of connections, and queries per second (QPS) reference value.

Instance specifications

The following tables list the specifications of a single shard. The overall performance of a cluster or read/write splitting instance can be calculated by using the following formula: Overall performance = Performance of a single shard × Number of shards.

Note
  • The enhanced SSDs (ESSDs) listed in these tables are used only to support the operation of the system, such as storing logs, supporting temporary file backup, and storing append-only files (AOFs). They are not intended for data storage.

  • For more information about the differences between the direct connection mode and the proxy mode that are supported by cluster instances, see Cluster master-replica instances.

  • Cloud-native cluster instances offer the freedom to adjust the number of shards. For more information, see Adjust the number of shards for an ApsaraDB for Redis cloud-native instance.

Shard specifications of non-cluster instances

Non-cluster instances are standard instances. The specifications listed in the following table are applicable to cloud-native standard instances.

Specification name

InstanceClass value (used in API operations)

CPU cores

Memory (GB)

ESSD capacity (GB)

Bandwidth (Mbit/s)

Maximum connections

QPS reference value

256 MB Community Edition

redis.shard.micro.ce

2

0.25

1

24

10,000

100,000

1 GB Community Edition

redis.shard.small.2.ce

2

1

5

48

10,000

100,000

2 GB Community Edition

redis.shard.mid.2.ce

2

2

10

96

10,000

100,000

4 GB Community Edition

redis.shard.large.ce

2

4

20

96

10,000

100,000

8 GB Community Edition

redis.shard.xlarge.ce

2

8

40

96

10,000

100,000

16 GB Community Edition

redis.shard.2xlarge.ce

2

16

80

96

10,000

100,000

24 GB Community Edition

redis.shard.3xlarge.ce

2

24

120

96

10,000

100,000

32 GB Community Edition

redis.shard.4xlarge.ce

2

32

160

96

10,000

100,000

64 GB Community Edition

redis.shard.8xlarge.ce

2

64

320

96

10,000

100,000

Shard specifications of cluster instances in direct connection mode

The specifications listed in the following table are applicable to cloud-native cluster instances in direct connection mode.

Specification name

InstanceClass value (used in API operations)

CPU cores

Memory (GB)

ESSD capacity (GB)

Bandwidth (Mbit/s)

Maximum connections

QPS reference value

1 GB Community Edition

redis.shard.small.ce

2

1

5

48

10,000

100,000

2 GB Community Edition

redis.shard.mid.ce

2

2

10

96

10,000

100,000

4 GB Community Edition

redis.shard.large.ce

2

4

20

96

10,000

100,000

8 GB Community Edition

redis.shard.xlarge.ce

2

8

40

96

10,000

100,000

16 GB Community Edition

redis.shard.2xlarge.ce

2

16

80

96

10,000

100,000

24 GB Community Edition

redis.shard.3xlarge.ce

2

24

120

96

10,000

100,000

32 GB Community Edition

redis.shard.4xlarge.ce

2

32

160

96

10,000

100,000

64 GB Community Edition

redis.shard.8xlarge.ce

2

64

320

96

10,000

100,000

Shard specifications of cluster instances in proxy mode and read/write splitting instances

The specifications listed in the following table are applicable to cloud-native cluster instances in proxy mode and cloud-native read/write splitting instances.

Specification name

InstanceClass value (used in API operations)

CPU cores

Memory (GB)

ESSD capacity (GB)

Bandwidth (Mbit/s)

Maximum connections

QPS reference value

1 GB Community Edition

redis.shard.with.proxy.small.ce

2

1

5

48

10,000

100,000

2 GB Community Edition

redis.shard.with.proxy.mid.ce

2

2

10

96

10,000

100,000

4 GB Community Edition

redis.shard.with.proxy.large.ce

2

4

20

96

10,000

100,000

8 GB Community Edition

redis.shard.with.proxy.xlarge.ce

2

8

40

96

10,000

100,000

16 GB Community Edition

redis.shard.with.proxy.2xlarge.ce

2

16

80

96

10,000

100,000

24 GB Community Edition

redis.shard.with.proxy.3xlarge.ce

2

24

120

96

10,000

100,000

32 GB Community Edition

redis.shard.with.proxy.4xlarge.ce

2

32

160

96

10,000

100,000

64 GB Community Edition

redis.shard.with.proxy.8xlarge.ce

2

64

320

96

10,000

100,000

Performance description

Architecture

Performance description

Standard instances

The overall performance of standard instances is the same as that described in the "Shard specifications of non-cluster instances" section.

Cluster instances in direct connection mode

Cluster instances in proxy mode

Read/write splitting instances

Overall performance of an instance = Performance of a single shard × Number of shards.

If an instance has four shards of the redis.shard.with.proxy.small.ce type, the following items show the performance of a single shard:

  • Number of CPU cores: 2

  • Bandwidth: 24 Mbit/s

  • Maximum number of connections: 10,000

  • QPS reference value: 100,000

The following items show the performance of the instance:

  • Number of CPU cores: 8

  • Bandwidth: 96 Mbit/s

  • Maximum number of connections: 40,000

  • QPS reference value: 400,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.

Bandwidth description

  • The bandwidths listed in the preceding tables are the bandwidths of individual shards. The total bandwidth of a cluster instance or read/write splitting instance is the sum of bandwidths of all shards in the instance.

  • The maximum bandwidth of cluster instances in proxy mode is 2,048 Mbit/s. After this upper limit is reached, the bandwidth does not increase even if the number of shards increases. Cluster instances in direct connection mode have no bandwidth limit.

  • The bandwidth value applies to the upstream and downstream bandwidths. For example, if the bandwidth of an instance is 24 Mbit/s, the upstream and downstream bandwidths of the instance are both 24 Mbit/s.

  • The bandwidths listed in the preceding tables are the internal bandwidths of instances. 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

Item

Description

Maximum number of connections

  • Proxy mode: The maximum number of connections to an instance is 500,000. After the upper limit is reached, subsequent connections cannot be established even if you add more shards or nodes.

  • Direct connection mode: The maximum number of connections to a shard is 10,000. The maximum number of connections to an instance can be calculated by using the following formula: Number of shards × 10,000.

Maximum number of new connections per second

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.

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 data shard is 2,000. If an instance has four data shards, the maximum number of new connections per second for the instance is 8,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 bandwidth of your instance is different from the bandwidth 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.