ApsaraDB for Redis provides multiple editions, series types, and architectures. This topic helps you find the references about the specifications of different instances.
References for instance specifications
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.
Enhanced Edition (Tair)
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.
DRAM-based instances support the classic (local disk-based) deployment mode.
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.
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 supports up to approximately 6,150 GB standard storage capacity.
Do I need to reserve memory for snapshots when I select specifications?
No, you do not need to reserve memory for snapshots when you select specifications. ApsaraDB for Redis resources are sold as Community Edition and Enhanced Edition (Tair) instances. 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.
Each specification type has a maximum QPS value. What happens if the QPS of an instance exceeds the maximum value?
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.
Why is a specific specification type unavailable?
The specification type may be phased out. For more information, see Retired instance types.
How do I check the specifications of an ApsaraDB for Redis instance by using InstanceClass?
You can enter the value of InstanceClass in the search box in the upper part of an Alibaba Cloud document to search for the specifications.
How do I test the performance of ApsaraDB for Redis instances?
You can test the performance of ApsaraDB for Redis instances by using the methods that are described in the performance whitepaper. For more information, see ApsaraDB for Redis Community Edition performance whitepaper.