We all know Jmeter isn't the best at changing the number of active threads during the run (unless you get fancy and make separate thread groups that fire off at different intervals).
Has any come up with a good solution for ramping down at the end of the test?
For example, I start with 50 threads and within 30 minutes I want 0 active threads.
The ramp-up period tells JMeter how long to take to "ramp-up" to the full number of threads chosen. If 10 threads are used, and the ramp-up period is 100 seconds, then JMeter will take 100 seconds to get all 10 threads up and running. Each thread will start 10 (100/10) seconds after the previous thread was begun.
Ramp up and ramp down helps us to test server auto scaling, as when server sees requests are on an increasing trend, it spins up more servers to manage the load.
Ans: The user ramp up decides the rate at which virtual users add to the load test whereas ramp down instructs LoadRunner at which rate virtual users exit from the load test. Example: Ramp-up rate – 5 Vusers per 10 seconds. Ramp-down rate – 20 Vusers per 5 seconds.
Check out Ultimate Thread Group here, I think this is it.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With