Based on customer experiences in stress testing, this document summarizes common performance issues and provides troubleshooting solutions and stress testing recommendations.
Applications Relied on by Real Servers Have Performance Issues
After a request reaches a real server through GWLB, the load on the real server is normal. However, because applications on real servers also rely on other applications such as databases, performance issues in the databases may also affect the stress testing performance.
A Real Server Is Unhealthy
It is easy to ignore the health status of the real server during stress testing. If the health check of the real server fails or the health check status fluctuates (sometimes good, sometimes bad, and changes repeatedly), it also leads to low performance during stress testing.
The Bandwidth of a Real Server Is Insufficient
If the real server has a low bandwidth, it cannot return packets to GWLB when the threshold is exceeded. At this time, GWLB will return a 504 or 502 error to the client.
The Bypass Security Group Feature Is Not Enabled for Real Servers
If the Bypass Security Group feature is not enabled for real servers, it will cause inaccessibility.
Stress Testing Recommendations
Note:
The following configurations are only used for GWLB stress testing. You do not need to have the same configurations in your production environment.
Disable the health check feature to reduce the access requests to real servers during health checks.
Use multiple client source IP addresses (greater than 5) for stress testing. Dispersed source IP addresses can better simulate actual online conditions.
Use multiple destination IP addresses (greater than 5) for stress testing. Dispersed destination IP addresses can better simulate actual online conditions.