Skip to main content

How to Understand LoadRunner Report

Web Resource Monitors



You obtain information about the performance of your Web server using
LoadRunner’s Web Resource monitor.

 
This chapter includes:
➤ About Web Resource Monitoring on page 

➤ Hits per Second Graph on page 
➤ Throughput Graph on page 
➤ HTTP Responses per Second Graph on page 
➤ Pages Downloaded per Second Graph on page 
➤ Retries per Second Graph on page 
➤ Connections Graph on page 
➤ Connections per Second Graph on page 
➤ SSLs per Second Graph on page


About Web Resource Monitoring
The Web Resource monitor enables you to analyze the throughput on the
Web server, the number of hits per second that occurred during the
scenario, the number of HTTP responses per second, the HTTP status codes
(which indicate the status of HTTP requests, for example, the request was
successful, the page was not found) returned from the Web server, the
number of downloaded pages per second, the number of server retries per
second, the number of open TCP/IP connections, the number of new TCP/IP
connections per second, and the number of SSL Connections per second.
Hits per Second Graph
The Hits Per Second graph shows the number of hits (HTTP requests) to the
Web server (y-axis) as a function of the elapsed time in the scenario (x-axis).
This graph can display the whole step, or the last 60, 180, 600, or 3600
seconds. You can compare this graph to the Transaction Response Time
graph to see how the number of hits affects transaction performance.
Throughput Graph
The Throughput graph shows the amount of throughput on the Web server
(y-axis) during each second of the scenario run (x-axis). Throughput is
measured in bytes and represents the amount of data that the Vusers
received from the server at any given second. You can compare this graph to
the Transaction Response Time graph to see how the throughput affects
transaction performance.
In the following example, the Transaction Response time graph is compared
with the Throughput graph. It is apparent from the graph that as the
throughput decreases, the transaction response time also decreases. The
peak throughput occurred at approximately 1 minute into the step. The
highest response time also occurred at this time.




Retries per Second Graph


The Retries Per Second graph shows the number of attempted Web server
connections (y-axis) as a function of the elapsed time in the scenario (x-
axis). A server connection is retried when the initial connection was
unauthorized, when proxy authentication is required, when the initial
connection was closed by the server, when the initial connection to the
server could not be made, or when the server was initially unable to resolve
the load generator’s IP address.


Connections Graph


The Connections graph shows the number of open TCP/IP connections (y-
axis) at each point in time of the scenario (x-axis). One HTML page may
cause the browser to open several connections, when links on the page go to
different Web addresses. Two connections are opened for each Web server.


This graph is useful in indicating when additional connections are needed.
For example, if the number of connections reaches a plateau, and the
transaction response time increases sharply, adding connections would
probably cause a dramatic improvement in performance (reduction in the
transaction response time).


Connections per Second Graph


The Connections Per Second graph shows the number of new TCP/IP
connections (y-axis) opened and the number of connections that are shut
down each second of the scenario (x-axis).


This number should be a small fraction of the number of hits per second,
because new TCP/IP connections are very expensive in terms of server,
router and network resource consumption. Ideally, many HTTP requests
should use the same connection, instead of opening a new connection for
each request.








SSLs per Second Graph


The SSLs per Second graph shows the number of new and reused SSL
Connections (y-axis) opened in each second of the scenario (x-axis). An SSL
connection is opened by the browser after a TCP/IP connection has been
opened to a secure server.


Because creating a new SSL connection entails heavy resource consumption,
you should try to open as few new SSL connections as possible; once you’ve
established an SSL connection, you should reuse it. There should be no
more than one new SSL connection per Vuser.


If you set your run-time settings to simulate a new Vuser at each iteration
(via the Browser Emulation tab in the Run-Time Settings menu), you should
have no more than one new SSL connection per Vuser per iteration. Ideally,
you should have very few new TCP/IP and SSL connections each second.

Comments

Popular posts from this blog

Why Driven Testing Important for every Software Tester

Context driven testing, Tester have to set their own path to complete their testing objectives, Test product, test documentation and test deliverable. The meaning of context-driven testing is project capture application of skill and opinion. Tester start testing with context driven testing it is very easy to understand and test application, therefore testing is a human activity that involves a great deal of skill to do well. The context-driven software testing methodological analysis indicates for continuous and creative valuation of testing opportunities. A tester always wants to do testing with context driven testing. It’s a very good practice to hands of explore and able to be proud of that work.   Why we need context driven testing- Context driven methodology like as agile process. Agile methodology generally depends on all-inclusive of unit tests. But in context driven testing, tester have to knowledge on unit testing as well testers will change, In context driven te...

Want to know about Mobile Application Testing? Came to right place

What is Mobile Application Testing ? Mobile Application Testing is a phenomenon of testing functionality, usability and consistency of application software designed for mobiles. It is done in two ways: Automated and Manually. When you buy a new mobile, various applications came pre-installed and some you install as per your need from mobile software distribution platforms such as Google Play, Nokia Store etc. In the recent years, mobile devices had shown a rapid growth rate .  Factors that give an open challenge to Mobile application Testing : 1. Mobile devices models : Different models have different hardware configurations, input methods (some are QWERTY, some are touch while others are normal). 2. Several different operating systems (OS) : Market  is full of availability of different operating  systems  (   Android , IOS, BREW, BREWMP, Symbian,   Windows Phone , and   BlackBerry   (RIM)).Each operating system is unique in ...

SELENIUM TESTING: SELENIUM IDE (& its installation)

In our previous post of selenium testing, we discussed selenium testing briefly. But it was just an introduction about that. And the selenium is much wider in its own. In today’s article, we are going to discuss the selenium, IDE Tool. What is Selenium IDE?? In selenium testing, selenium IDE (Selenium Integrated Development Environment) is a simple tool present in selenium suite Selenium IDE has an inbuilt record and playback functionality that allow us to create tests very quickly, easily and efficiently. Selenium IDE is very easy to install and use. As selenium IDE is a Firefox plugin, it aims to support Firefox browser only. Therefore, we can execute our created test scripts on Firefox only. Selenium IDE supports auto complete mode which allows the user to: * Enter commands more quickly *Restricts the user to enter invalid commands. The most impressive thing about the Selenium IDE in selenium testing that the user need not to have any prior knowledge of pr...