This topic describes the specifications of persistent memory-optimized instances of ApsaraDB for Redis Enhanced Edition (Tair), including the instances in the standard or cluster architecture. These specifications include the memory capacity, maximum number of connections, and maximum bandwidth.
Purchase an instance
- persistent memory-optimized instance
- Persistent memory-optimized instances adopt Intel® Optane™ DC persistent memory (AEP) to provide you with in-memory databases that have a large capacity and are compatible with open source Redis. A persistent memory-optimized instance does not use disks to implement data persistence. It saves up to 30% of costs compared with an ApsaraDB for Redis Community Edition instance and provides almost the same performance in terms of throughput and latency. This helps improve the reliability of business data. For more information, see Persistent memory-optimized instances.
Enhanced solid-state disks (ESSDs) of Alibaba Cloud. For more information about the related terms and performance levels of ESSDs, see
Note ESSDs are used only to store system operating data, such as logs and backup data. ESSDs are not used as the media to read or write data.
|Standard||The overall performance of standard instances is as described in the instance specifications table.|
|Cluster||The overall performance equals the number of shards multiplied by the performance of each shard. For example, a cluster instance has four shards of the tair.scm.standard.4m.32d type, which is the first instance type in Instance specifications. The following items show the performance of each shard:
The following items show the overall performance of the cluster instance:
|Instance type||InstanceClass that is used in API operations||Specifications||ESSD performance level||Maximum number of concurrent connections||Maximum bandwidth value (MB/s)|
|Number of CPU cores||Memory (GB)||AEP (GB)||ESSD (GB)|
|Master-replica 4 GB volatile memory and 8 GB persistent memory||tair.scm.standard.2m.8d||6||2||8||24||PL1||30,000||96|
|Master-replica 4 GB volatile memory and 32 GB persistent memory||tair.scm.standard.4m.32d||6||4||32||96||PL1||30,000||96|
|Master-replica 8 GB volatile memory and 32 GB persistent memory||tair.scm.standard.8m.32d||6||8||32||96||PL1||30,000||96|
|Master-replica 16 GB volatile memory and 64 GB persistent memory||tair.scm.standard.16m.64d||6||16||64||192||PL1||30,000||96|
|Master-replica 32 GB volatile memory and 128 GB persistent memory||tair.scm.standard.32m.128d||6||32||128||384||PL1||30,000||96|
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.