1

I am using JMeter to loadtest a webapplication. We are using realistic throughput values based on Google Analytics. Each functionality has to deal with a different throughput level (eg. some pages are visited more than others)

Right now I do a test per functionality, one after the other. Which is not ideal. I'm using the Throughput Shaping Timer plugin to control the amount of requests per minute.

How in JMeter can I set different levels of throughput for different transaction controllers in one test? Is this even possible?

Improve this question
1

JMeter timers have their scope. Basically if you put a timer on the same level with all requests - it will impact all of them, if you put the timer as a child of the certain request - it will affect only this particular request.

So it is possible to shape requests throughput individually. Even more, you can change throughput during test run if you'll use a JMeter Property as a throughput value and control it via Beanshell server Check out How to use JMeter's Throughput Constant Timer guide for more details.

Improve this answer
2
  • thanks for your answer and sorry for my late response. I have used the constant throughput timer before, also as child of certain requests. The problem: lets say the first request needs a throughput of 60RPM and the second 30 RPM. And I set Loop Count: forever. The first request wil receive the correct amount of throuhput the first time, and so will the 2nd request. But on the second loop there won't be enough threads to run the first request as they are still queuing for the 2nd request which passes threads at half speed – Charlie Apr 1 '15 at 9:37
  • Are your requests dependent on each other? Can you separate out your requests into different thread groups? – RaGe Apr 23 '15 at 15:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.