Skip to main content

How to Understand Load Runner Report Web Resource Monitors

By
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.

Comments

Post a Comment

Popular posts from this blog

Steps To Hunt the Bugs Successfully

By
The testers should catch the bugs in software that they’re testing. Testers should try to catch as several vital bugs as soon as possible. Catching the crucial bug earlier on Product-Life-Cycle can save the Projects from financial losses & mitigate the risks as compared for catching the same at a later stage in SDLC. Steps to hunt the bugs: Sometimes it’s useful to break the rules: The following test cases, which were predefined a tester can miss the bugs so it makes it impossible’s to provide the product i.e. 100 percent bug free. If you-follow pre-determined test cases you risks becoming blind to outside the bugs. A first secret is to check the functionality under the test. It’ll be an effective channel to discover the more bugs, because functionality is not generally covered by the test cases. Examine the patterns: You might have noticed that the bugs can be often met in the groups, one can call them-gregarious. The testing a new but the similar functionality...
Post a Comment
Read more

Cross browser testing Tools

By
Cross Browser testing It is a process to test the web apps across multiple browsers. It involves the checking compatibility of the app across multiple web browsers & ensures that your web app’s works correctly across different web browsers. Tools for Cross Browser Testing Browser shots: The browser shots might be most exhaustive cross browser-testing tool that exists. Browser Shots includes all of most popular-browsers, like Firefox, Chrome, & Safari, along with the tons of another browser’s that might sound unfamiliar, like Sea Monkey, Flock, & Iceape. You can adjust the resolution, color-settings, & even Flash and JavaScript settings. Cross Browser Testing: It allows users to test their websites with over the hundred resolution or browser and Operating System combinations. This also has support to mobile web-browsers, which is crucial because the web traffic is making shift from the primarily desktop computer users to primarily mobile ...
Post a Comment
Read more

Mobile Application Testing: Strategy for Development

By
There are a huge number of demands and lots of competitions in the mobile application industries. In that demands and competitions, the mobile application testing has become more important. The testing phase of the mobile application testing looks like evil between the creative process and excitement of new products in the market. According to the survey, “In US, on an average 2-3 hours per day people spends their time on smartphones and tablets. On that time, they spent 80% on mobile application and remaining 20% on web applications.” Few list of key factors for successful mobile application testing strategies are: Selection of Device for Testing : Before introducing the mobile application test activities, first select the devices for testing the application. Selection decision is very important because only devices can help to targets maximum numbers of the customers for accessing the application. There are two parts for device selection: §   Device Model ...
Post a Comment
Read more