Monitoring the Load Test
While creating load on an application, you want to see how the application performs in real time and where potential bottlenecks exist. You use LoadRunner’s suite of integrated monitors to measure the performance of every single tier, server, and component of the system during the load test.LoadRunner includes monitors for a variety of major backend system components including Web, application, network, database, and ERP/CRM servers.
1. View the default graphs.
By default, the Controller displays the Running Vusers, Transaction Response Time, Hits per Second, and Windows Resources graphs. The first three don’t require configuration. The Windows Resources monitor has been configured for you for this test.
=> Running Vusers - whole scenario graph lets you monitor the number of Vusers that are running at a given time. You can see that the Vusers gradually start running at a rate of 2 Vusers every 1 minute.
=> Transaction Response Time - whole scenario graph lets you monitor the amount of time it takes for each transaction to be completed. You can see how long it takes for your customers to log on, search flights, purchase flights, check itineraries, and log off the system.
You can see that as more and more Vusers work on the application under test, transaction response times increase and the level of service provided to the customer degrades.
=> Hits per Second - whole scenario graph lets you monitor the number of hits (HTTP requests) on the Web server made by Vusers during each second of the scenario run. This enables you to follow the amount of load that is generated on the server.
=> Windows Resources graph lets you monitor the Windows resource usage measured during a scenario (such as CPU, disk, or memory utilization).
You will learn how to configure Windows Resources and other monitors , “Creating a Load Testing Scenario.”
Notice that each measurement appears on a color-coded row in the graph legend. Each row corresponds to a line in the graph with the same color.
Selecting a row highlights the corresponding line in the graph, and vice versa.
2. View error information.
If your machine is handling a heavy load, you may encounter errors.
Select the Errors Statistics graph in the Available Graphs tree, and drag it into the Windows Resources graph pane. The Error Statistics graph provides details about the number of errors and the time at which they occurred during the scenario. Errors are grouped by source for example, the location in the script or the load generator name.
In this example, you can see that after 5 minutes, the system starts to encounter an increasing number of errors. These errors are caused by timeouts due to degrading response times.
Note: It will take your scenario a few minutes to run. You can go back and forth from the graphs to the Vusers as your scenario proceeds to display your results online.



No comments:
Post a Comment