Run time settings in load runner
what is the use of "Stimulate new user on every iteration".I mean in what scenarios we ll be using this option.Till now I 've not used this option so interested the use of it.Do we use this option when we have less number of user licenses (guess). thank you for the replies .
I'm not a load runner user, so I could be wrong about this.
When you perform iterations, you can usually choose between keeping the session data between iterations, or throwing it out and starting a new session. it's the difference between simulating 1 person say doing the same action over and over again 100 times, vs. 100 people waiting in line to do the same action.
Keeping the same session is good for say soak testing to see if there may be memory leaks associated with a user with a long running session. Where using new users can stress prioritization and resource management. For example, 1 user drops off and another user arrive. Does the system keep say a running process associated with the first user? (This is one of the areas where Apache is weak)
the real issue here is simuilating your user base...
if your users log on and stay logged in all day doing multiple iterations (ie log on is in vuser_init() and log off in vuser_end()) or you have captive users, who will never (or very raerly) clear down their cookies/cache then do not use simulate a new user on each iteration
if you have users randomly coming in from the wild then use simulate a new user on each iteration
both can find memory leaks...
the important thing is simulating how YOUR users behave, as this will show the behaviour of the application with your users