ApsaraDB for Redis does not allow you to adjust the number of CPU cores. You can change the instance architecture or add more nodes or shards to improve the overall performance of an instance. If the CPU load of an ApsaraDB for Redis Community Edition or ApsaraDB for Redis Enhanced Edition (Tair) instance is high, you can troubleshoot and optimize CPU-intensive commands, hotkeys, and large keys, and rule out the possibility of abnormal traffic patterns. If the CPU load remains high even after you perform the preceding operations, you can refer to this topic to improve the overall CPU performance of the instance and ensure smooth business operations.
Confirm the edition, deployment mode, and instance type of an instance
The CPU specifications supported by an instance vary based on the edition, deployment mode, and instance type of the instance. Before you upgrade the CPU specifications, check the information about the instance.
Log on to the ApsaraDB for Redis console and go to the Instances page. In the top navigation bar, select the region in which the instance that you want to manage resides. Then, find the instance and click the instance ID.
In the Basic Information section of the Instance Information page, view the following information: Edition, Instance Type, Deployment Mode, and Read/Write Splitting.
NoteFor different instances, the UI terms and positions of Edition, Instance Type, Deployment Mode, and Read/Write Splitting in the Basic Information section may slightly vary. The actual UI terms in the console prevail.
Standard instances
ApsaraDB for Redis Community Edition instances and Tair DRAM-based and persistent memory-optimized instances
Confirm the series type and architecture of an instance
On the Instance Information page, make sure that the instance meets the following requirements:
The name of the instance type does not contain Cluster or Read/Write Splitting.
If the Read/Write Splitting switch is displayed, the switch is turned off. If the Read/Write Splitting switch is not displayed, you can ignore this requirement.
If the Edition parameter is set to Tair (ApsaraDB for Redis Enhanced Edition), the series type is DRAM or Persistent Memory.
Methods to improve CPU performance
The CPU specifications of a single shard in a standard instance cannot be modified. You cannot add more cores to scale up the CPU capacity of a shard. However, you can change the architecture to improve the overall performance of the instance:
If your workloads are read-heavy and do not have high requirements for data consistency, you can switch to the read/write splitting architecture. You can enable read/write splitting and increase the number of read replicas to improve the overall CPU performance of the instance.
For information about how to change the architecture of a cloud disk-based instance to read/write splitting, see Enable read/write splitting.
For information about how to change the architecture of a local disk-based instance to read/write splitting, see Change the configurations of an instance.
NoteYou can view the deployment mode in the Basic Information section of the Instance Information page. For more information, see Confirm the edition, deployment mode, and instance type of an instance.
If your workloads require high data consistency, you can switch to the cluster architecture. You can increase the number of shards to improve the overall CPU performance of the instance. For more information, see Change the configurations of an instance.
Tair ESSD/SSD-based instances
Confirm the series type and architecture of an instance
On the Instance Information page of the instance, make sure that the Edition parameter is set to Tair (ApsaraDB for Redis Enhanced Edition) and the Version parameter is set to ESSD.
Methods to improve CPU performance
You can change the shard specifications to improve CPU performance. For more information, see Change the configurations of an instance .
Cluster instances
Confirm the series type and architecture of an instance
On the Instance Information page, make sure that the name of the instance type contains Cluster.
Methods to improve CPU performance
The CPU specifications of a single shard in a cluster instance cannot be modified. You cannot add more cores to scale up the CPU capacity of a shard. However, you can increase the number of shards to improve the overall performance of the instance.
For information about how to increase the number of shards for a cloud disk-based instance, see Adjust the number of shards for an instance.
For information about how to increase the number of shards for a local disk-based instance, see Change the configurations of an instance.
Read/write splitting instances
Confirm the series type and architecture of an instance
On the Instance Information page, make sure that the name of the instance type contains Read/Write Splitting or the Read/Write Splitting switch is turned on.
Methods to improve CPU performance
The CPU specifications of a read/write splitting instance cannot be modified. You cannot add more cores to scale up the CPU capacity. However, you can increase the number of read replicas to improve the overall performance of the instance.
For information about how to increase the number of read replicas for a cloud disk-based instance, see Enable read/write splitting.
For information about how to increase the number of read replicas for a local disk-based instance, see Change the configurations of an instance.
References
For information about how to troubleshoot and address high CPU utilization, see Troubleshoot high CPU utilization on an ApsaraDB for Redis instance.
For information about the performance of ApsaraDB for Redis Community Edition and ApsaraDB for Redis Enhanced Edition (Tair), see Performance white paper.
For information about the instance type, CPU cores, memory, bandwidth, and maximum allowed number of connections of ApsaraDB for Redis Community Edition and ApsaraDB for Redis Enhanced Edition (Tair) instances, see Overview.