5

What's the difference between Number of Threads and the Constant Throughput Timer? Before I heard of the Constant Throughput Timer, I thought that if I wanted to simulate 21 requests per minute , the following configuration was enough :

enter image description here

but now that I found this post, I'm not so sure.

This is my new configuration now that I make use of the Constant Throughput Timer :

enter image description here

enter image description here

  1. Does the Constant Throughput Timer override the parameters specify in Thread Group (Number of threads,Ramp-up period, etc) ?
  2. Why even making use of the Constant Throughput Timer I sometimes get a number of requests higher than the value specify in the Target Throughput (21 in the above image)
  3. If a indicate a value of 21 in the Target Throughput, isn't this constant supposed to guarantee a maximum value of 21 requests? If so why do I sometimes get more requests than indicated.

All your comments and ideas will be appreciated. enter image description here

P.S. I'm also using a Runtime controller.

enter image description here

Improve this question

1 Answer 1

Reset to default
3

No, it regulates the number of requests going to & response received from the server per minute.

As stated in the Jmeter user guide "the throughput value should not be changed too often during a test - it will take a while for the new value to take effect."

http://jmeter.apache.org/usermanual/component_reference.html#Constant_Throughput_Timer

The issue you have shown above will always happen in the first minute of the test run.

hope this will help.

Improve this answer
Sign up to request clarification or add additional context in comments.

5 Comments

So it is completely normal too have an extra request the first time we run our test plan? That is, if I specify x as the Target Throughput, I will always get x+1 requests in the first executions of the test plan? Is it mentioned somewhere in the documentation?
I'm having this same issue. Is there any explanation why this happens the first time we run a test plan? I don't think I've seen anything mentioned in the documentation
"the throughput value should not be changed too often during a test - it will take a while for the new value to take effect." this above line is mentioned in the documentation, so no matter what you do, during the first run it will always be X+1.
I am trying to understand the difference between 1) 100 virtual users and Constant Throuput timer as 600 requests per minute and 2) 200 virtual users and Constant Throuput timer as 600 requests per minute
I too have this question, as eddy asked #1 Does the Constant Throughput Timer override the parameters specify in Thread Group (Number of threads,Ramp-up period, etc) ?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.