| || |
Analysis - Page Download Time
I am bringing up this questiona again. In the Analyis component, I want clarification on the Network times and server times.
According to LR documentation on "Time to first buffer"
"First Buffer Displays the amount of time that passes from the initial HTTP request (usually GET) until the first buffer is successfully received back from the Web server. The first buffer measurement is a good indicator of Web server delay as well as network latency."
Also, the "Receive Time" is "Receive Displays the amount of time that passes until the last byte arrives from the server and the downloading is complete.
The Receive measurement is a good indicator of network quality (look at the time/size ratio to calculate receive rate). "
I am not mentioning Client, Connection, DNS, Error under Page download time breakdown as they are null for the load test.
Now, if my response time for a transaction (time for a transaction added for a get/post operation is 3.021 secs
Receive time is 2.955 secs. Should I consider the difference between these as .066 as the Server Time.
My questions are:
1) LR is giving Receive time as 2.955 secs out of 3.021 secs (which is response time for a transaction).
Is the receive time the total network time. Plz mind that we do not have a "Network Delay monitor" for this license wherin we could have
monitored the network delay from one server to another.
2) Does the Receive time include the database server or is it only for the receive time from the web-servers to the client machines??
We also have the SQL profiler statistics for SP's( SQL Server 2000) and we are not exactly able to deduce the Database time taken from the total response times.
Provide pointers for this.
Re: Analysis - Page Download Time
You have made a number of statements and asked a number of questions - but I will offer the following:
Since you don't have network delay monitors installed - you can use tracert to measure the network performance from one point to another.
Run it several times with no load, and then again with load. (eg from app server to web server or app server to data base server.)
You can use ping to measure effective bandwidth "ping -l 2048 <ip address>". It will tell you how long it takes to send 2KB of data. Run this with no load and with load to see if bandwidth bottleneck exists under load.
What is contained in the receive time is dependant on the way that the system has been designed. For example, if a user submits login details to a web page, but some content is immediately returned (before the user details have been processed then you can not conclude very much about internal processing from the users perspective.
The receive time is only only based on what is seen by LoadRunner, (running the VUGen script), which is the web server / client interaction. Web server to APP or Database server activty is not directly measured by VUGen, but can be measured using LoadRunner monitors.
You might like to read a brief discussion on 'response time' at http://loadtest.com.au/Terminology/ResponseTime.htm which may shed some light on your questions.