Joel

• Oct 3rd, 2006

 

after the test has executed successfully, look for Analyze Results on the menu.

Ashwajatha

• May 23rd, 2007

 

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.

reddygma

 Profile Answers by reddygma 

• Dec 5th, 2008

 

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.