ApsaraDB for Redis:Overview

References for instance specifications

Description

Specifications of ApsaraDB for Redis Community Edition cloud-native instances (recommended)

• If an instance uses the standard architecture, the instance provides up to 64 GB of memory and supports up to approximately 100,000 queries per second (QPS).

• If an instance uses the read/write splitting architecture, the instance provides up to 64 GB of memory and supports up to approximately 600,000 QPS.

• If an instance uses the cluster architecture, the instance provides up to 16,384 GB (64 GB × 256 shards) of memory. The overall performance of the instance is calculated by using the following formula: Number of shards × Performance per shard. The performance of each shard is determined by the shard specifications.

Specifications of ApsaraDB for Redis Community Edition classic instances

• A standard master-replica instance is deployed in the master-replica architecture. Each instance provides up to 64 GB of memory and supports up to approximately 80,000 QPS. This maximum QPS value is for reference only.

• For a cluster master-replica instance, each data shard is deployed in the master-replica architecture. Each instance provides up to 4,096 GB (16 GB × 256 shards) of memory and supports up to approximately 25,600,000 QPS. This maximum QPS value is for reference only.

• A read/write splitting instance consists of a master node and one or more read replicas. Each instance provides up to 64 GB of memory and supports up to approximately 600,000 QPS.

Retired instance types

ApsaraDB for Redis instances of specific specification types are no longer available. If you have purchased one or more of these instances, you can continue to use them. For information about the specifications of these instances, such as the maximum number of connections, maximum bandwidth value, and maximum QPS value, see Retired instance types.

Series type

Description

DRAM-based instance

DRAM-based instances use the multi-threading model. A DRAM-based instance provides the read and write performance approximately three times that of a Community Edition instance with the same specifications.

• If the instance uses the standard architecture, the instance provides up to 64 GB of memory and supports up to approximately 300,000 queries per second (QPS).

• If the instance uses the read/write splitting architecture, the instance provides up to 64 GB of memory and supports up to approximately 1,800,000 QPS.

• If the instance uses the cluster architecture, the instance provides up to 16,384 GB (64 GB × 256 data shards) of memory and the instance performance is calculated by using the following formula: Number of data shards × Performance per data shard. The performance of each data shard is determined by the shard specifications.

DRAM-based instances support the classic deployment mode.

• Standard master-replica architecture: uses the multi-threading model and provides approximately three times the performance of a Community Edition instance with the same specifications. Each instance provides up to 64 GB of memory and supports up to approximately 240,000 QPS.

• Read/write splitting architecture: uses the multi-threading model, runs in the master-replica architecture, and consists of a master node and one or more read replicas. A read/writing splitting instance provides approximately three times the performance of a Community Edition instance with the same specifications. Each instance provides up to 64 GB of memory and supports up to approximately 1,440,000 QPS.

• Cluster architecture: uses the multi-threading model and provides approximately three times the performance of a Community Edition instance with the same specifications. Each data shard uses the master-replica architecture. Each instance provides up to 4,096 GB (16 GB × 256 data shards) of memory and supports up to approximately 61,440,000 QPS. This maximum QPS value is for reference only.

Persistent memory-optimized instance

The instance does not use disks to implement data persistence. The instance provides almost the same performance as a Community Edition instance in terms of throughput and latency while persisting each operation. A standard persistent memory-optimized instance is only about 70% the price of a Community Edition instance.

• If the instance uses the standard architecture, the instance provides up to 64 GB of memory and supports up to approximately 100,000 QPS.

• If the instance uses the read/write splitting architecture, the instance provides up to 64 GB of memory and supports up to approximately 600,000 QPS.

• If the instance uses the cluster architecture, the instance provides up to 16,384 GB (64 GB × 256 data shards) of memory and the instance performance is calculated by using the following formula: Number of data shards × Performance per data shard. The performance of each data shard is determined by the shard specifications.

ESSD-based instance

An ESSD-based instance runs in the master-replica architecture. The instance reduces up to 85% of costs compared with a Community Edition instance. The instance is suitable for the storage of warm and cold data and scenarios that require compatibility with Redis, large capacity, and high access performance. Each instance provides up to 192 GB of memory and has a standard storage capacity of up to 6,150 GB.