Configuring Slow Start (Dedicated Load Balancers)

Scenarios

You can enable slow start for HTTP or HTTPS listeners. After you enable it, the load balancer linearly increases the proportion of requests to send to backend servers in this mode. When the slow start duration elapses, the load balancer sends full share of requests to backend servers and exits the slow start mode. Slow start gives applications time to warm up and respond to requests with optimal performance. When the health check function is enabled, slow start takes effect after backend servers are detected healthy. If the health check is not working normally during the slow start, the slow start duration will not stop.

Backend servers will exit slow start in either of the following cases:

1. The slow start duration elapses.
2. Backend servers become unhealthy during the slow start duration.

If an unhealthy backend server exits slow start, it will enter slow start again once it is detected healthy.

Prerequisites

• You have created a dedicated load balancer.
• You have added an HTTP or HTTPS listener to the dedicated load balancer.

Procedure

1. Log in to the management console.
2. In the upper left corner of the page, click and select the desired region and project.
3. Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
4. On the Load Balancers page, locate the dedicated load balancer that you have created and click its name.
5. In the Backend Server Groups tab, click Add Backend Server Group.
6. Enable Slow Start and set the slow start duration. Set other parameters based on service requirements.
7. Click OK.

Follow-Up Operations

• For an existing backend server group, you can click on the right of the backend server group on the Backend Server Groups tab page to enable slow start.
• Add backend servers to the newly added backend server group by performing the operations in Adding or Removing Backend Servers (Dedicated Load Balancers).