Search code examples
jmeterperformance-testingload-testingjmeter-5.0

Target Throughput behavior of Constant Throughput Timer in JMeter


As per the Documentation - "Of course, if the server is not able to handle such a load, the throughput will be lower." How is this behavior handled and throughput calculated?

Suppose I set the target throughput as 1500/min but my system could handle only 1000/min, what kind of feedback behavior is expected by JMeter and how is the total throughput affected?

Will the JMeter still try to achieve 1500/min with higher error rate (for failed requests) or JMeter shoots the throughput to 1500/min but gradually comes back near to 1000/min based on certain factors like error rate? If yes, what are the factors determining this step-down, any insight/reference to understand this step-down behavior?


Solution

  • Either you do not have enough threads in the test plan to achieve your desired TPS or your application response time is higher.

    The total number of requests you will be able to make through JMeter depends on your application response time.

    So you will need at least 25 threads to achieve 1500/min if your average response time is 1 second (assuming there is only 1 request).

    If throughput isn't increasing even after providing with enough threads but the response time increasing and some of your requests got failed, then this indicates the performance bottleneck!