Performance Testing:Why do synchronizing timer settings take effect locally but not in PTS?

Causes

The synchronizing timer feature takes effect only in a load generator. During the stress testing in PTS, JMeter may automatically allocate multiple load generators. Therefore, synchronizing timer settings in JMeter do not take effect in PTS. PTS supports JMeter distributed adaptation settings. You can specify whether synchronizing timer settings take effect globally or on a load generator in the JMeter script. For more information, see the "Step 1: Create a JMeter scenario" section of the Create a JMeter scenario topic.

To use the synchronizing timer feature, take not of the following items:

• The Number of Simultaneous Users to Group by value does not exceed the number of concurrent sets on a load generator. 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 load generator 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.