All Products
Search
Document Center

Performance Testing:Specify the number of IP addresses from which the testing traffic originates

Last Updated:Jun 26, 2025

The source IP address refers to the IP address from which the performance testing traffic originates. If a significant number of requests are sent from a single IP address at a high frequency, the protection mechanism may recognize this behavior as abnormal and take steps to block the traffic. You can increase the number of source IP addresses within the specified range based on the number of virtual users or RPS. By distributing the load across a greater number of IP addresses, you can minimize the risk of traffic blocking.

Procedure

  1. Log on to the PTS console, choose Performance Test > Create Scenario, and then click PTS.

  2. Set the number of IP addresses from which the testing traffic originates.

    Important
    • Additional IP addresses increase costs. Virtual Users per Minute (VUM) = Number of IP addresses × 500. View the estimated VUM consumption in the figure on the right.

      Number of IP addresses = Number of load generators (each supports ≤ 500 concurrent virtual users).
      500: Billing calculates each IP address at 500 virtual users, regardless of actual test concurrency. For more information, see Pay-as-you-go.
    • If your IP capacity is insufficient, submit a ticket to request an increase.

    image

Causes of performance testing exceptions

  • SLB limits

    Check whether the Server Load Balancer (SLB) instance reaches or exceeds the specifications and bandwidth limits based on its billing method. If the SLB instance is at the outermost layer of the service architecture and the testing API uses HTTPS or has session persistence enabled, a 503 error may occur during stress testing. If no traffic or log appears at the backend, the 503 error may be caused by the limit of the SLB instance on the number of requests from a single IP address. To resolve the issue, see 503 (Service Unavailable).

  • Anti-DDoS or WAF enabled

    If Anti-DDoS or WAF is enabled, traffic interception may occur. Take one of the following measures based on your business requirements:

    Temporarily disable Anti-DDoS or WAF during performance testing. For more information, see FAQ Overview.

    Add whitelists in the PTS console to prevent testing from being blocked. For more information, see What do I do if the stress testing traffic cannot access my web application due to security policies?

  • Content Delivery Network (CDN) or Dynamic Content Delivery Network (DCDN) used

    submit a ticket when your business is reaching or exceeding the existing peak.

What can I do if the load of the load generator cluster is high?

If the load generator cluster is under heavy loads and its resources such as the bandwidth, CPU, or memory are insufficient, you can increase the number of testing traffic source IP addresses.