JMeter Ram Up

Today I have read one article about Ram Up period in JMeter. And I think that it necessary for everyone who research about JMeter.

Ramp up period property in jmeter is not very clear to new comers. From the documentation

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. If there are 30 threads and a ramp-up period of 120 seconds, then each successive thread will be delayed by 4 seconds.
Ramp-up needs to be long enough to avoid too large a work-load at the start of a test, and short enough that the last threads start running before the first ones finish (unless one wants that to happen).

Here are some examples of ramp up time which we have used
Number of threads(users) = 11
Ramp up period(in seconds) =  110
Loop Count = 1
Every 10 second(110/11) one request hits the server.
Starts with one request initially
Number of threads(users) = 11
Ramp up period(in seconds) = 660
Loop Count = 1
Every 60 second(660/11) one request hits the server
Starts with one request initially
Number of threads(users) = 11
Ramp up period(in seconds) = 660
Loop Count = 3
Every 60 second(660/11) 3 request hits the server
Starts with 3 request initially
Start with Ramp-up = number of threads and adjust up or down as needed.
If you want to do a concurrent load test
Number of threads(users) = 300
Ramp up period(in seconds) = 0
Loop Count = 1
By default, the thread group is configured to loop once through its elements.


HoaLe