is there any Specific Formula for Calculating Pacing based on TPS or Vusers??
--
You received this message because you are subscribed to the Google "LoadRunner" group.
To post to this group, send email to LR-Loa...@googlegroups.com
To unsubscribe from this group, send email to
LR-LoadRunne...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/LR-LoadRunner?hl=en
Time between beginning of one iteration to the next =
[ Universal_constant * #Seconds_in_your_sample_window/ (# Samples_in_your_sample_window(Requirements)/#Users_for_your_business_Process(Requirements) ) * (.8|1.2) / Universal_Constant ]
Pacing = 0 generally indicates an absence of a load model and a failure in the requirements phase of the project. The client server model dictates that not all users will be active at any given time and that in the inter-request interval from client A that other clients requests may be serviced. An individual user being idle due to think time of pacing does not mean that the backend system is idle, for in this interval other requests are being serviced for other virtual users.
James Pulley, http://www.loadrunnerbythehour.com/PricingMatrix
From: lr-loa...@googlegroups.com [mailto:lr-loa...@googlegroups.com] On Behalf Of Gaurav Mishra
Sent: Sunday, March 06, 2011 10:14 AM
To: lr-loa...@googlegroups.com
Subject: Re: Pacing calculation
i have a doubt on this part.your pacing formula is absolutely correct but don't you think that due to this it is possible that our system will be idle for a long time. I mean it may be possible that transaction get complete before end of pacing time. so that much time system would be idle. can't we do something to reduce this time. i mean put some variables at time of scripting. which would check running time of script.put pacing as 0. now when ever sufficient time have spent and script is done, next would start on it's own. am i right?
--
The below method of pacing is good but there are multiple ways
Usually your goal in load test is to achieve targetted transaction volume right?
Then, first see how long your script takes to execute with out think time or pacing
Then ask the avg visit length of the user for that flowfrom you sme
Adjust the think time or pacing to match the script duration with the visit length
Then next calculate conncurent users
With the think time and pacing + theconcurent users, you should reach the target transaction volume
Or
I saw one of my colleque never use thank time or pacing
That method is also correct to reproduce consistant tests with cost effectiveness. But that will not be realistic test.
With realistic test it is difficult to produce the defect at the same time because we use ramdomizations for ft and pacing
I hope this helps
Load Modeling is a basic skill, like learning double entry accounting. If
your trainer/mentor isn't covering this subject as a part of your
training/professional development then find another one.
James Pulley, http://www.loadrunnerbythehour.com/PricingMatrix
Declaration:
T = Total amount of Think time in the script
I = Expected/Target iteration
R = Residual time of the test window.
R = ( D - (T + B)*I)
P = Pacing interval
Dividing the residual time by target iteration gives pacing interval
is there any Specific Formula for Calculating Pacing based on TPS or Vusers??
--
“what this means : I = Expected/Target iteration...”
This means that it is time to go back to school on performance requirements.
Related disciplines which will provide value here are:
· Budgeting.
· Sales Projections
· Database analysis on the growth of data in the system : what types and how fast?
· WAN use growth
· Web server log analysis. How often is each page hit? Can a growth curve be projected?
· Systems engineering related to the sizing of hardware
James Pulley, http://www.loadrunnerbythehour.com/PricingMatrix
From: lr-loa...@googlegroups.com [mailto:lr-loa...@googlegroups.com] On Behalf Of Rao Gadde
Sent: Monday, March 07, 2011 11:14 PM
To: lr-loa...@googlegroups.com
Subject: Re: Pacing calculation
CHAITANAYA