Can any one say the concept of virtual users concurrent execution for multiple iterations.
I want to know like, when the virtual users are doing many iteration will it wait for the response of the previous iteration and then do the next iteration or it will just carry on with the execution. If so how can i confirm this?
In runtime settings->Pacing I can see "Start newIteration as soon as the previous iteration ends".
so is one iteration ends when it gets the response back or what is the concept behind this?
Quick response are appreciated. Thanks
1. What version of LoadRunner (LR) or PerformanceCenter (PC) are you using?
2. What is the protocol you are recording?
2.1 If .NET, which version of .NET does the app require?
2.2 If .NET, which version of .NET do you have installed?
2.3 If OracleNCA with Oracle Forms Server, please list the version of Oracle Forms Server. You can get this info from the main Oracle Form when launched - Help -> About
3. If HTML - are you using HTML-Advanced with URLs or,
4. If URL mode:
- Concurrent groups, or
- Without Concurrent groups?
5. Which LoadRunner/PerformanceCenter feature (FPs) or service packs are you using?
6. VuGen Recording - are you using Old or New Recording Engine?
7. What kind of LoadRunner license do you have -
9. What platform(s) (PCs) and Operating Systems (Windows-XP, etc.)? Include version and service packs (SP1 or 2, etc.)
You can confirm what is happening by turning on your logs (full logging) and reading them. LoadRunner will wait for the system to respond to the current request (or will time out), before moving on to the next. Once it completes an iteration of the script (once all the transactions have completed) it will look at the Run Time Settings to determine whether to just continue right away with the next iteration of the script (no delay in pacing), or wait the specified interval before coninuing. If you look at your replay log, you will see something like "waiting xxx seconds for iteration pacing" - I forget the exact verbage here.
Your best bet for understanding this is, as I say, reading the logs and playing with the settings, and reading the logs again to see what sort of difference it made.
If you are new to LoadRunner, as it sounds by your question, this is an excellent way of getting familiar with what is happening in the script. It is tedius but a good learning experience. Read the logs - they are your friend!! [img]/images/graemlins/cool.gif[/img]
SoCalGal - Defender of end user response times!