Manually increase the bandwidth of an instance - Tair (Redis® OSS-Compatible)

When your business is about to experience traffic spikes during promotional events such as flash sales, if the default bandwidth of your Tair (Redis OSS-compatible) instance is insufficient, you can manually increase the bandwidth of the instance without changing its specifications to easily handle these traffic spikes.

Function overview

Because different instance types have different bandwidth limits, traffic exceeding the bandwidth limit may cause blocking, which affects service performance. Compared to changing instance specifications, adjusting bandwidth helps you quickly increase bandwidth, save overall costs, and avoid connection interruptions, allowing for immediate use.

Scenarios

In the following scenarios, you can adjust the bandwidth of an instance to prevent network congestion and performance deterioration.

Expand to view detailed application scenarios

Application scenario	Description
Handle traffic spikes	You can adjust the bandwidth of your instance to handle traffic spikes during promotional events such as a flash sale. After these events end, you can decrease the bandwidth of the instance to reduce costs.
Mitigate impacts on your business	If many read and write operations are performed on large keys within a short period of time, you must temporarily increase the bandwidth of the instance to mitigate impacts on your business and to reserve time for processing these operations.
Deal with request skew issues at low costs	If the instance is a cluster or read/write splitting instance, some data shards or read replicas of the instance are frequently accessed. As a result, the bandwidth usage of these data shards or read replicas frequently reaches the allocated bandwidths. However, the bandwidth usage of other data shards or read replicas is low. In this case, you can increase the bandwidths of specific data shards or read replicas instead of increasing the bandwidth or changing the specifications of the instance.
Increase the bandwidth of a standard instance	If the instance is a standard instance of the highest specifications and the bandwidth of the instance does not meet your business requirements, you can increase the bandwidth of the instance without the need to upgrade the instance to a cluster instance. This lets you focus on business growth.

Billing

You are charged on an hourly basis based on the amount of extra bandwidth that you purchase and the duration for which you use the extra bandwidth. The billing standards vary by region. For more information, see Billing items.

Note

You are not charged for the default bandwidth that is provided for the instance type. You are charged only for the extra bandwidth that you purchase.

Feature limits

The bandwidth of an instance or a shard can be increased by up to six times the default bandwidth of the instance, but the increase in bandwidth cannot exceed 192 Mbit/s. For example, the default bandwidth of a 2 GB memory-optimized standard Tair instance is 96 Mbit/s. The bandwidth of this instance can be increased by up to 192 Mbit/s. The maximum bandwidth of this instance is 288 Mbit/s. The default bandwidth of a 256 MB standard Redis Open-Source Edition instance is 10 Mbit/s. The bandwidth of this instance can be increased by up to 60 Mbit/s. The maximum bandwidth of this instance is 70 Mbit/s.
If you need a higher bandwidth, you can upgrade the specifications of your instance or upgrade the architecture of your instance (for example, from the standard architecture to the cluster architecture) to obtain higher bandwidth performance. For more information, see Instance specifications.

If you perform one of the following operations, the purchased extra bandwidth automatically becomes invalid and your money is refunded. You can re-increase the bandwidth for your instance as needed.

Operation	Exception
Major version upgrade	None
Change the configurations of an instance	If the instance uses the standard architecture, the bandwidth settings remain valid after you change the specifications of the instance.
Change the zone of an instance	If the instance uses the standard architecture, the bandwidth settings remain valid.

Procedure

Log on to the 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 Configuration Information section, click Modify next to Bandwidth MB/s.
Note
- In the Configuration Information section, you can view the maximum internal bandwidth of the instance. If the instance is a cluster or read/write splitting instance, the bandwidth is the sum of the bandwidths that are allocated to all data nodes within the instance.
- During off-peak hours, you can reduce the bandwidth to save resources and reduce costs. For information about how to view the traffic usage of an instance, see View monitoring data.

In the panel that appears on the right, select the extra bandwidth that you want to purchase for the data node and click OK.

Key configuration item

Description

Adjust Bandwidth

The extra bandwidth that you want to purchase. The bandwidth of an instance can be increased up to six times the maximum bandwidth available for the instance type. For information about the maximum bandwidth available for each instance type, see Instance specifications. The maximum extra bandwidth that you can select varies based on the instance type.

If the instance is a standard instance, adjust the bandwidth of the instance.
If the instance is a cluster or read/write splitting instance, select one of the following options:
- Adjust Bandwidth for All Shards: Increase or decrease the bandwidth of all shards in the instance, for example, to handle potential traffic spikes during promotional events such as flash sales.
- Adjust Bandwidth for Individual Shards: Adjust the bandwidth of one or more specific shards in the instance, for example, to eliminate request skew in the instance. You can adjust the bandwidth of specific shards based on traffic skew.
  Note
  You can use the instance diagnosis feature to analyze whether request skew exists. For more information, see Diagnose an instance.

Click Pay and complete the payment process as prompted.
After you complete the payment, wait for about 1 minute. Then, the maximum bandwidth of the instance is updated to the sum of the existing bandwidth and the extra bandwidth that you purchase.
If you want to cancel the extra bandwidth that you purchased, you can follow the preceding steps to readjust the bandwidth and click Pay.

What to do next

We recommend that you use the Auto Scaling feature for bandwidth. This feature automatically increases or decreases the bandwidth of an instance when the bandwidth usage reaches the threshold. This reduces costs and improves O&M efficiency.
To schedule bandwidth upgrades for your Tair instance, see Schedule bandwidth upgrades for a Tair instance.
If your instance is a Redis Open-Source Edition instance and you need to increase the bandwidth by a large amount, we recommend that you use Tair (Enterprise Edition). The maximum bandwidth supported by each specification of Tair instances is 96 Mbit/s or higher.

Related APIs

API operation	Description
EnableAdditionalBandwidth	Adjusts the bandwidth of an instance.

FAQ

Q: Why can't I find the Maximum Bandwidth button?
A: Tair (Enterprise Edition) disk-based instances do not support modifying the default bandwidth.
Q: Why is the maximum bandwidth limited to three times the default bandwidth?
A: You may have purchased subscription bandwidth plans for the instance. Go to the My Orders page to find the corresponding order (the order ID is Instance ID-bw, for example, r-2zew****qs67bqho3n-bw), and unsubscribe from it. Then, follow the instructions in this topic to purchase pay-as-you-go bandwidth plans. This lets you increase the maximum bandwidth up to six times the default bandwidth of the instance.
Q: How do I adjust the bandwidth of a specific data shard or data node within a cluster or read/write splitting instance?
A: When you adjust the bandwidth, you can select Adjust Bandwidth for Individual Shards and adjust the bandwidth of one or more specific shards as needed. This provides more flexibility in handling skewed service traffic.
Q: Does a bandwidth adjustment cause transient connections?
A: No. It is ready to use out of the box.
Q: How do I unsubscribe from the extra bandwidth that I purchase for my instance?
A: Move the bandwidth adjustment slider to the leftmost position to decrease the bandwidth of your instance to the value provided for the instance type. Then, check the estimated cost and complete the payment.
Q: If I change the configurations of my instance after I purchase a specific amount of extra bandwidth, am I still charged for the extra bandwidth?
A: If you change the configurations of a standard instance after you purchase a specific amount of extra bandwidth, the extra bandwidth remains valid and you are charged for the extra bandwidth. The bandwidth of your instance is the sum of the bandwidth that is provided for the new instance type and the extra bandwidth that you purchase. For other instance architectures, the extra bandwidth that you purchase becomes invalid and you are no longer charged for the bandwidth after you change the configurations of your instance. In this case, you must adjust the bandwidth of the instance again if needs arise. For information about the bandwidth limits of each instance type, see Instance specifications.