All Products
Search
Document Center

Performance Testing:Why does a configured rendezvous point not take effect in JMeter?

Last Updated:Oct 30, 2024

Problem description

You have a configured rendezvous point in the JMeter script. However, the configured rendezvous point does not take effect during the stress testing in Performance Testing Service (PTS).

Causes

The rendezvous point in JMeter takes effect only within a load generator. For more information, see Synchronizing Timer. JMeter in PTS may automatically allocate multiple load generators. Therefore, we recommend that you do not use the synchronizing timer feature. To use the synchronizing timer feature, take not of the following items:

  • Globally Effective is turn on for the synchronizing timer feature.

  • The Number of Simultaneous Users to Group by value does not exceed the number of concurrent sets on a stress tester. Otherwise, relevant conditions cannot be met. We recommend that you set the value to 0, which indicates that the maximum number of concurrent sets on a stress tester is automatically used by default.

  • An appropriate value is specified for Timeout in milliseconds. This way, if a certain time is reached, the concurrent sets are released at the same time even if the specified number of concurrent sets is not reached.

    For example, you need to collect 2,000 sets and release them at the same time to simulate a spike scenario and set the timeout period to 5,000 milliseconds. In your actual stress testing, only 1,500 sets are collected within the specified timeout period. In this case, the system continues to execute the testing to release the sets after the timeout, and does not indefinitely wait.