SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 3 of 3
  1. #1
    Member
    Join Date
    Jun 2008
    Posts
    133
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Run time settings in load runner

    Hi All,

    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 .

  2. #2
    SQA Knight
    Join Date
    May 2006
    Location
    Playa Del Rey, California, United States
    Posts
    2,596
    Post Thanks / Like
    Mentioned
    17 Post(s)
    Tagged
    1 Thread(s)
    Total Downloaded
    0
    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)
    David Lai
    SDET / Consultant
    LinkedIn profile

  3. #3
    Moderator
    Join Date
    Feb 2010
    Location
    Europe
    Posts
    944
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0
    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

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 10.71%
vBulletin Optimisation provided by vB Optimise v2.6.4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.2.8 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 04:15 PM.

Copyright BetaSoft Inc.