This topic describes how to configure an elastic scaling policy for an ApsaraDB MyBase instance to handle traffic spikes in scenarios such as the 618 promotion and Double 11.
Double 11 is an online shopping festival in China. During Double 11, the number of access requests to your database instances significantly increase within a short period of time. In this case, the elastic scaling feature of ApsaraDB MyBase can help you handle traffic spikes during peak hours. The elastic scaling feature temporarily upgrades the memory and CPU specifications of your instance to improve the instance performance. After the specified period of time ends, ApsaraDB MyBase automatically restores the instance to the specifications before the upgrade.
For example, an e-commerce platform receives 100,000 visits per day on average. In this case, an instance with the specification of 2 cores and 16 GB memory can ensure stable operations. However, statistics show that the number of visits to the platform during Double 11 can reach one million. To handle the peak traffic, you can configure an elastic scaling policy to temporarily upgrade the instance to the specification of 8 cores and 64 GB memory.
- Log on to the ApsaraDB MyBase console.
- In the top navigation bar, select the region where the instance that you want to manage is deployed.
- In the left-side navigation pane, click Clusters. On the page that appears, find the dedicated cluster in which the instance is deployed and click Details in the Actions column.
- In the left-side navigation pane, click Instances. Find the instance that you want to manage and choose in the Actions column.
- In the Elastic Configuration panel, configure the following parameters.
Parameter Description Instance Information The basic information about the instance. You can view the following information:
- Instance ID
- Maximum Connections
Resource Type The type of the resource that you want to upgrade. You can select one of the following resource types:
Set up resources The quantity of the resource after the upgrade. The resource is specified in the Resource Type parameter. Deadline of temporary dispatching The time when the resource restores to the specification before the upgrade. Restore to specification original configuration Specifies whether to cancel upgrading the resource that you select. If you want to cancel upgrading the specified resource, click the check box for this resource.Note Skip this parameter if you do not need to cancel upgrading the specified resource.Note The parameters for elastic scaling vary based on the database engine. You can view the parameters in the ApsaraDB MyBase console.
- Click OK.
- Click the ID of the instance. On the Basic Information page, navigate to the Instance Resources section and view the current resource configuration.