To handle sudden or expected traffic spikes, you can temporarily increase the upper limit of bandwidth throttling on the Instance Information page in the console.
If big keys are used or the traffic generated during peak hours exceeds the upper limit of bandwidth, network congestion may occur on the nodes. This affects the service performance. In this case, you can temporarily adjust the upper limit of bandwidth. This allows you to spend more time to optimize the memory architecture and fix big keys issues. You can also handle peak traffic during time-limited promotions and focus on business improvement.
Bandwidth adjustment rules
- The temporary adjustment is valid for at least seven days and expires at 00:00 after
the seven days. For example, if you adjust the upper limit of bandwidth at 10:00 on
January 1, the adjusted upper limit expires at 00:00 on January 9.
Note For more information about how to permanently adjust bandwidth, see Change specifications.
- After the adjustment, the upper limit of bandwidth is doubled. For example, if the upper limit of bandwidth for an instance is 10 MB/s, the upper limit is increased to 20 MB/s after the adjustment.
- Upgrade the major version or the minor version of cluster instances.
- Upgrade or downgrade specifications for all instances or migrate the instances across zones.
- Log on to the ApsaraDB for Redis console.
- On the top of the page, select the region where the instance is deployed.
- On the Instances page, click the Instance ID of the instance.
- In the section, click Temporarily Adjust Bandwidth.Note For a cluster or read/write splitting instance, the value of Maximum Internal Bandwidth shows the maximum internal bandwidth of the cluster.