Monday, 20 October 2014

This following point helps to get the information about the performance of your Web server using Load Runner’s Web Resource monitor.
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

What is Web Resource Monitoring?
The Web Resource monitor to provide the power of  you, to analyze the output on the web server,  and the number of push (hits) per second that occurred during the scenarios, or the number of HTTPs reactions per second, and the HTTP’s status codes returned from Web server, & the number of downloaded pages per second, or the number of server re-tries per second, the number of opens TCP/IP connection’s, the number of new TCP/IP connection’s per second, and the number of SSLs Connection per second.

Hit per Second Graphs
The Hits of per Second graph displays the number of hits to the Web server as the function of passed time in the scenarios. This graph can show the full step, & the last 60, 180, 600, and 3600 seconds. You can proportion this graph to the (Transaction Response Time) graph to look how the number of hits affects to the transaction performance.

Throughput of the Graph
The capacity of the graph shows the amount of throughput on the Web server during every second of the scenarios executes. Throughput is also measured in bytes or represents the amount of information’s that user’s received from the server at any given second. You can proportion this graph to Transaction Response Time graph to view, how the throughput affects to the transaction performance.

Re-tries per Second Graph
Retries per Second graph displays the number of the attempted Web server connections as a function of the passed time in the scenarios. A server connection is re-tried when the starting connection was un-authorized, and when proxy authentication is needed, when the starting connection was closed through the server, when the opening connection to the server could not be made, and when the server was initially incapable to resolve the load generators’ IP addresses.

Connections to the Graph
Connections graph displays the number of opens TCP/IP connections at all points in the time of scenarios. One the HTML page may reason of the browser to opens the several connections, when links on the pages go to the different Web addresses. The two connections are opened for all Web servers. This graph is very useful in pointing, when additional connections are required.

Connection per Second Graph
A Connection per Second graph displays the number of new TCP/IP connections opened & the number of connection’s that are shut down every second of the scenarios. This number should be in small fractions of the number of hits per second, because the new TCP/IP connection is very expensive in terms of servers, router or network resource consumptions. Ideally, many of HTTP requests should use the common connections, instead of initially a new connection for all requests.

Secured Sockets Layer (SSL) connections per second
Number of SSL connections opened per second, after TCP/IP connections of SSL connection is opened. SSLs connection has bulky (heavy) resources consumptions. If we selects the, simulate a new user at every iteration then there should not be more than of one SSL connection per second.

0 comments:

Post a Comment

Bookmark Us

Delicious Digg Facebook Favorites More Stumbleupon Twitter