Response Time

End to End Response Time : It Means total time that a user wait for a Response after submitting a Request .

End-to End Response Time = GUI Response Time + N/W + Server Response Time

Response Time is More means : 

• It might be Network Problem,
• It might be System Issue
• It might be LG Issue
• It might be Application Code : (Memory Leak, Large Object, Heavy Functions, etc..)
• It might be slow DB qry.
• It might be Application Issue :  eg : If we submit one page, that page is taking more time to loading because that page is having more Data.
• High Physical Disk Queue length.
• Throughput is down
• Memory Leak
• CPU Utilization is more.

Note :- If we increase Pacing Time and Think Time the Response Time will be Increase and Throughput is Decrease
            If we decrease Pacing Time and Think Time the Response Time will be decrease and Throughput is Increase

Eg :- Pacing Time = 5sec   Think Time = 5sec Response Time =3sec

            here 5+5+3 = 13sec / one transaction that means

            60/13 = 4.5 transaction/1 min ------> Throughput

         Pacing Time = 3sec   Think Time = 3sec Response Time =2sec

            here 3+3+2 = 8sec / one transaction that means

            60/8 = 7.5 transaction/1 min ------> Throughput

Note : For which Transaction is taking more response time, we need to analyze these graphs 

1. web page Diagnostics Graph
2. Page Breakdown Graph

High Response Time may cause less Hits/Sec
Qus :- Response time is taken more time for two transactions and less time is taken for other transactions ?
Ans : Hence we need analyse in server side for those two transactions and check in Application side and check the Application as manually for those two transactions.

Response Time Graph merging with other Graphs :-

Response Time is more means : It might be Network problem or LG issue or System issue or Application Issue.

eg :- Application Issue : Suppose if we submit one page,  that page taking more time, Because that page having more data.

-> Four key graphs used during LoadRunner analysis to analyze Response Time.

1. Transaction summary report.

2. AVG Transaction Response Time graph.

3. Transaction/ sec graph

4. Transaction Response Time underload.

1.Response Time Graph Merging with Number of Users Graph :-

    To check how the Number of running Vusers affects the Transaction response time.

Whenever the Response time improved due to a decrease in the Vuser Load.

2. Merge the Response time Graph and Running Vuser graph : Here we can find exactly after what user transaction taking more response time, once you find the point which transaction taking more Response Time and what is user load at that particular point of time.

3. Response Time graph Merging with Throughput Graph :-

Increase the Response time with constant Throughput may be due to network bandwidth issue.

If you see the decrease in Throughput with the Increase in Response Time then Investigate of the server end.

If Response Time extremes poor means we need to take Thread Dump for Analysis.

4. Response Time Graph Merging with Error Graph :-

-> Here we can early identify the exact time when the first error occurred as well as the time until the error log.

->We can also check whether the Response Time increases after 1st Error appeared.

-> Increase in error % during Ramp up indicates the error due to user load.

-> If error identified during mid of steady state it indicates Queue file-up at the server.

Qus :- Response Time is taken more for two Transactions and less time taken for other transactions ?

Ans : Here we need to analyze in server side for these two transactions and check in a application side and check the application as manually for those two transactions.

-> If transaction Response time more means we need to analyze 

    1. Web page Diagnostics Graph

    2. Page Breakdown graph.

-> whenever you identify high Response time along with Memory Leakage. so  first carryout HeapDump analysis and check the frequency of GC and carryout the GC analysis to identify root cause analysis.

High Response Time along with Memory Leakage :-  Here first carryout HeapDump analysis and check frequency of GC.

-> If your Response Time is High and your Threads goes to the ideal the CPU usage may also will be high.

 

Qus:- If i run the scenario with 1 hour for 10 Iterations, I want to know the time each Transaction took rather then AVG Response Time ?

Ans : Check the Raw Data from the AVG Transaction Response Time Graph.

Look under the Menu View -> View Raw Data and then choose entire scenario time. This will bring up a side bar, Click on it and it will display all the Response Time items.

It will also show a little flappy disk icon with it you can save an XLS file with all that data which will include on Transaction Response Time.

Qus :- How to get the Response Time of each request inside in the single transaction for any particular user Action ?

Ans :- Go to Runtime Settings -> Misc -> Each action as a Transaction so that we will get Response Time for Each Request.

Qus : Is Load Runner capture Failed Transaction Response Time ?

Ans :- No, The Load Runner capture the only Passed Transactions Response Time.

Qus :- Why the Response Time showing difference in Loadrunner and Dynatrace ?

Ans :- The Loadrunner capture the only passed Transactions Response Time but

            The Dynatrace capture the Passed and Failed Transactions Response Time.