GeekInterview.com
  I am new, Sign me up!
 
GeekInterview.com  >  Tech FAQs  >  LoadRunner
Go To First  |  Previous Question  |  Next Question 
 LoadRunner  |  Question 10 of 143    Print  
Hello,

I want to know about '' Analysing the Results'' of Loadrunner.How to understand perforamnce of the Application by the graphs obtained?

  
Total Answers and Comments: 3 Last Update: December 05, 2008     Asked by: Subraja 
  
 Sponsored Links

 
 Best Rated Answer

No best answer available. Please pick the good answer available or submit your answer.
October 03, 2006 01:28:53   #1  
Joel        

RE: Hello,I want to know about '' Analysin...
after the test has executed successfully look for Analyze Results on the menu.
 
Is this answer useful? Yes | No
May 23, 2007 04:16:37   #2  
Ashwajatha        

RE: Hello,I want to know about '' Analysin...
Analysis can be Understood by comparison of 2 or more Graphs use Overlay method to compare Transaction Response time with {vuser throughput ...etc} there by u can understand to some extent the flaws/Bottle necks.

 
Is this answer useful? Yes | No
December 05, 2008 01:18:28   #3  
reddygma Member Since: November 2008   Contribution: 15    

RE: Hello,I want to know about '' Analysing the Results'' of Loadrunner.How to understand perforamnce of the Application by the graphs obtained?
LR is having very powerful Analysis engine that will give almost all types of results that you need to analyze for your performance results. Even if you create a graphs or Analysis alysise results by combining one or more graphs together to know the potential problem bottle necks in the applications.

Some of them are

1. Top time transactions (separate top most transactions by response time).
2. Transactions failures (Consider if Passed >90 then consider it is valid performance result else probably may have potential functional bottlenecks at the level of load).
3. synchronous graphs and spikes in the response and throughput graphs.
4. User ramp up and ramp down
5. Transaction response time(any spikes that deviates quite an extended average or baseline control limit then take a closer look)
6. At the end of load testing always look manually application and server logs to get the potential errors.(e.g. out of memory dead locks null pointer exceptions and etc).

Hope I think it will help you.

 
Is this answer useful? Yes | No


 
Go To Top


 Sponsored Links

 
About Us -  Privacy Policy -  Terms and Conditions -  Contact -  Ask Question -  Propose Category -  Site Updates 

Copyright © 2005 - 2009 GeekInterview.com. All Rights Reserved

Page copy protected against web site content infringement by Copyscape