ApsaraDB for Redis provides multiple editions, series types, and architectures. This topic helps you find the references about the specifications of different instances.

Instance types that support local disks

This topic lists the references that describe the specifications of ApsaraDB for Redis instances based on editions, series types, and architectures. You can find the detailed specifications of an instance type by clicking a link in the Reference column in the following table.

Edition Series type Reference Overview
Community Edition None Master-replica standard instances A master-replica instance of ApsaraDB for Redis. The maximum memory is 64 GB, and the maximum queries per second (QPS) is about 80,000. This maximum QPS value is for reference only.
Master-replica cluster instances A cluster instance of ApsaraDB for Redis. Each shard is deployed in a master-replica architecture. The instance with the highest specifications contains 32 shards and supports 512 GB of memory. The maximum QPS is about 2,560,000. This maximum QPS value is for reference only.
Read/write splitting instances A read/write splitting instance of ApsaraDB for Redis that contains a master node and one or more read replicas. The instance with the highest specifications contains five read replicas and supports 64 GB of memory.
Read/write splitting cluster instances (retired) A read/write splitting instance of ApsaraDB for Redis that contains a cluster and one or more read replicas. A read replica is attached to each shard in the cluster. The instance with the highest specifications contains 32 shards and 32 read replicas, and supports 512 GB of memory.
Overview Performance-enhanced instances Standard instances A standard master-replica instance that uses the multi-threading model and provides a performance about three times that of a Community Edition instance of the same specifications. The maximum memory is 64 GB, and the maximum QPS is about 240,000. This maximum QPS value is for reference only.
Cluster instances A cluster instance of ApsaraDB for Redis that uses the multi-threading model and provides a performance about three times that of a Community Edition instance of the same specifications. Each shard uses a master-replica architecture. The maximum memory is 4,096 GB, and the maximum QPS is about 61,440,000. This maximum QPS value is for reference only.
Read/write splitting instances A read/write splitting instance of ApsaraDB for Redis that uses the multi-threading model, runs in a master-replica architecture, and contains a master node and one or more read replicas. A read/writing splitting instance provides a performance three times that of a Community Edition instance of the same specifications. The instance with the highest specifications contains five read replicas and supports 64 GB of memory.
Persistent memory-optimized instances Standard instances and cluster instances An instance that uses the standard architecture or the cluster architecture. 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.
Storage-optimized instances Standard instances A storage-optimized instance that runs in a master-replica architecture. The instance reduces up to 85% of costs compared with a Community Edition instance. The instance is suitable for scenarios that store warm and cold data, and require compatibility with Redis, large capacity, and high access performance.
Retired instance types N/A N/A ApsaraDB for Redis instances that are phased out. If you have purchased one or more of these instances, you can continue to use them. For more 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.

Instance types that support cloud disks

Edition Series type Reference Overview
Community Edition None Community Edition with cloud disks A Community Edition instance that uses the standard architecture or the cluster architecture.
  • If the instance uses the standard architecture, the maximum memory is 64 GB and the maximum QPS is 100,000.
  • If the instance uses the cluster architecture, the maximum memory is 2,048 GB and the instance performance is the product of shard quantity and performance per shard specified by shard specifications.
Enhanced Edition (Tair) Performance-enhanced instances Performance-enhanced instances A performance-enhanced instance that uses the standard architecture or the cluster architecture. The instance uses the multi-threading model, provides up to 64 GB of memory, and supports about 240,000 QPS. It provides a performance about three times that of a Community Edition instance.
Persistent memory-optimized instances Persistent memory-optimized instances A performance-enhanced instance that uses the standard architecture or the cluster architecture. 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.
Storage-optimized instances Standard instances A storage-optimized instance that runs in a master-replica architecture. The instance reduces up to 85% of costs compared with a Community Edition instance. The instance is suitable for scenarios that store warm and cold data, and require compatibility with Redis, large capacity, and high access performance.

FAQ

  • Q: Do I need to reserve memory for snapshots when I select specifications?

    A: No, you do not need to reserve memory for snapshots when you select specifications. ApsaraDB for Redis resources are sold as instances of the Community Edition and Enhanced Edition (Tair). You do not need to reserve memory for snapshots. The memory capacity of each specification type is the maximum memory that is available to you. The memory capacity includes the memory occupied by user data, the static memory consumed by your instance, and the memory occupied by network connections.

  • Q: Each specification type has a maximum QPS value. What happens if the QPS of an instance exceeds the maximum value?

    A: This may cause an accumulation of requests. If the QPS reference value is exceeded for an extended period of time, we recommend that you choose higher specifications. For more information, see Change the configurations of an instance.

  • Q: Why is a specific specification type unavailable?

    A: The specification type may be phased out. For more information, see Retired instance types.

  • Q: How can I check the specifications of an ApsaraDB for Redis instance by using InstanceClass?
    A: You can enter the value of InstanceClass in the search box at the top of an Alibaba Cloud document.
  • Q: How do I test the performance of ApsaraDB for Redis instances?

    A: You can test the performance of ApsaraDB for Redis instances by using the methods that are described in Performance White Paper. For more information, see Test environment