I find that it is a lot simpler to Calculate Throughput based on 'This Thread Only'. That option basically means if I set the CTT to a value of 60 and only have 1 thread then I will get a throughput of 1 request per second. If I have 2 threads I will get 2 requests a second, 3 threads = 3tps, etc.
You still need to factor in concurrency when planning this as well as the fact that longer response times will potentially prevent the CTT from achieving what you tell it to. In direct answer to your question, yes, it sounds like you have a bottleneck of some sort. The reason why it stops at 60,000 and not some other value is probably just because your response times increase and this slows down the throughput. It might be that a higher value is possible under a different configuration (more threads trying more often) but really, the more important question is why are the response times increasing! If you change the test to be more aggressive then you actually make it harder to identify the problem - slow and gradual is, generally, better for finding breakpoints compared to hard and fast. ----- http://www.http503.com/ -- View this message in context: http://jmeter.512774.n5.nabble.com/Constant-throughput-timer-not-giving-expected-results-tp4784904p4785802.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
