Load Runner Tips: Report generation in load runner, Analysis in Load runner, adding graph in load runner report, merging graph in LR, filtering result in LR, export result in Excel, export result in PDF, export result in Word, export result in HTML, Performances testing, Load Runner, LR testing, performances tuning, performances monitoring

Load Runner Analysis Tips

Analysis :
Analysis component of load runner is used for correlating result of load testing and generate report by using data gather in Controller. After analyzing the Average Transaction Response Time graph, we investigate the reason for high response time at particular instant and using graph auto correlation we come to conclusion that there was some system memory shortage at that particular moment
Analysis Graphs Analysis tool shows reports and graphs of the data captured from system under test. There are many graphs like,

Running Vusers
Hits per Second
Throughput
Average Transaction Response Time
Windows Resources

Merging Graphs

You can merge graphs to see the effect of one parameter on other. There are 3 ways to merge graph
Overlay: View contents of 2 charts that share a common X Axis.
Tile: View the contents of 2 charts that share a common X Axis, one above the other.
Correlate: Plot Y axis of two charts against each other

Filter Reports

Using filter functionality we can filter report for particular duration, transaction etc.

Export Report :

It allow user to export performance report into word, excel, pdf and any user specific format.

The goal of analysis is to find out bottlenecks in the application under test and then investigate the source of bottlenecks.

What was the average transaction response time?
What was the status of server resources when response time was high?
Did we meet the SLA?
What component of the system is responsible for decrease in performance?
Can we investigate the possible cause of the bottleneck by correlating the performance related data of the system and providing the solution to overcome it?

Components
The object-oriented SiteScope components fall into six broad categories: Webpage, Scheduler, Monitor, Alert, Script Alert and Reports.

The Webpage feature displays the browser-based user interface.
The Scheduler specifies when each monitor (such as each device or server status tracking process) runs.
The Monitor gathers statistics for each monitored device or server.
The Alert module sends e-mail, pager messages and SNMP alerts when SiteScope detects a problem.
The Script Alert program can run a script, restart a background service or run an external program when a problem occurs.
The Reports code generates Web pages that contain network statistics in a graphical or tabular format.


	Load Runner Analysis Tips Analysis : Analysis component of load runner is used for correlating result of load testing and generate report by using data gather in Controller. After analyzing the Average Transaction Response Time graph, we investigate the reason for high response time at particular instant and using graph auto correlation we come to conclusion that there was some system memory shortage at that particular moment Analysis Graphs Analysis tool shows reports and graphs of the data captured from system under test. There are many graphs like, Running Vusers Hits per Second Throughput Average Transaction Response Time Windows Resources Merging Graphs You can merge graphs to see the effect of one parameter on other. There are 3 ways to merge graph Overlay: View contents of 2 charts that share a common X Axis. Tile: View the contents of 2 charts that share a common X Axis, one above the other. Correlate: Plot Y axis of two charts against each other Filter Reports Using filter functionality we can filter report for particular duration, transaction etc. Export Report : It allow user to export performance report into word, excel, pdf and any user specific format. The goal of analysis is to find out bottlenecks in the application under test and then investigate the source of bottlenecks. What was the average transaction response time? What was the status of server resources when response time was high? Did we meet the SLA? What component of the system is responsible for decrease in performance? Can we investigate the possible cause of the bottleneck by correlating the performance related data of the system and providing the solution to overcome it? Components The object-oriented SiteScope components fall into six broad categories: Webpage, Scheduler, Monitor, Alert, Script Alert and Reports. The Webpage feature displays the browser-based user interface. The Scheduler specifies when each monitor (such as each device or server status tracking process) runs. The Monitor gathers statistics for each monitored device or server. The Alert module sends e-mail, pager messages and SNMP alerts when SiteScope detects a problem. The Script Alert program can run a script, restart a background service or run an external program when a problem occurs. The Reports code generates Web pages that contain network statistics in a graphical or tabular format.
	FIND MORE ON LOAD RUNNER TIPS \| About Load Runner \| Creating scripts in Load Runner \| Load Runner scenario \| LR Analysis \| Performance Tuning \| Performance Testing \| LR Errors \| Interview Question \| Load Runner Tool \| Correlation Practice \| Site Map \|