Hi, A ramp up period is necessary when your application can't handle all user connexions at the same time. Connecting everybody at the same time usually does a useless stress on the server, that will generates bad response times, server hang, or worse, total failure. Because the servers have to create all the application context / thread / memory increase at once.
To prevent that behaviour, ramp up is a good idea. Especially as in real life, users does not connect all at once. As for the timings, whith 5 users, and a ramp up of 5s, with 300s duration: - after 5s, all your threads will be started - start rate at 1 / second approximately - each thread will last 300s - your test will end at 300 + 5 (time of last thread start) : that is to say : 305 s Play with it! Rgds, Tibo On Wed, Apr 14, 2010 at 17:10, prasanna bhat <[email protected]>wrote: > Hi, > > Description of Ramp Up period in the user manual : > This property tells JMeter how long to delay between starting each user. > For > example, if you enter a Ramp-Up Period of 5 seconds, JMeter will finish > starting all of your users by the end of the 5 seconds. So, if we have 5 > users and a 5 second Ramp-Up Period, then the delay between starting users > would be 1 second (5 users / 5 seconds = 1 user per second). If you set the > value to 0, JMeter will immediately start all users. > > Usecase description: > I have 5 users in the thread, a Ramp Up period set to 5 sec and the > duration set to 300 sec in the Scheduler configuration. So for the first 5 > seconds each thread is invoked with a delay of 1 sec, but is the same > behavior(next thread is delayed for 1 sec) exhibited for the next 300 secs > of test duration? > > And also i was not clear as to how Ramp Up period is advantageous? and > when > to (and when not to) set this Ramp Up period? > > Thanks, > Prasanna >
