Analysis of various indices of LoadRunner results

transactions (user transaction analysis)
User transaction analysis is the basic performance analysis of the user's perspective.

1, transation sunmmary (Business Overview)
Comprehensive analysis of transactions is the first step in performance analysis, through analyzing the success and failure of user affairs in time,

Can directly determine whether the system is operating normally.

2, Average transacitonresponse time (transaction average response times)
"Transaction average response time" shows the average time spent in transaction execution per second during the test scenario run,

It can analyze the performance trend of the application system during the running of the test scenario.
Example: With the change of test time, the speed of system processing transaction begins to slow down, which indicates that the overall performance will decrease with the change of production time.

3, transactions per Second (through transaction number/tps)
"/tps per second" shows the number of passes, failures, and stops for each second of the scene, making it an important parameter to examine system performance. It can be used to determine the time transaction load of the system at any given time.

The analysis of TPs mainly depends on the performance trend of the curve.
Comparing it to the average transaction response time, you can analyze the impact of the number of transactions on the execution time.
Example: When the pressure increases, the click Rate/tps curve if the change is slow or there is a flat trend,

It is most likely that the server is starting to have bottlenecks.

4, total transactions Persecond (number of transactions per second)
"Total transactions per second" shows the total number of transactions passed in each second when the scene is running,

The failed department and the total number of transactions stopped.

5, Transaction performancesunmmary (Transactional energy summary)
Transactional summary shows the minimum, maximum, and average execution times for all transactions in the scenario.

Can directly determine whether the response time meets the requirements of the user.
Focus on the average and maximum execution time of the transaction, if its scope is not within the user's acceptable time range,

Cause analysis is required.

6, Transaction Response timeunder Load (transaction response time and load)
Transaction response time and load is a combination of the running virtual user diagram and the average response transaction time diagram.

It can be seen that the relationship between the response time and the number of users at any point.

Thus, the performance data of the system in user concurrency are mastered, which provides reference for the extended user system.

This diagram can look at the overall impact of virtual user load on execution time.

Useful for analyzing test scenarios that have a gradient load.

7, Transaction responsetime (percentile) (transaction response time (percent))
"Transaction response time (percent)" is a comprehensive analysis of the analysis based on the test results,

This is the chart that the tool indirectly obtains through some statistical analysis methods.

It allows you to analyze the percentage of transactions that can be performed within a given transaction response time span.

8, Transaction ResponseTime (distribution) (Transaction response time (distribution))
Transaction response Time (distribution) shows the distribution of the time that a transaction takes to execute during a scene's operation,

It allows you to understand the number of transactions in different response times during testing.

If the system has predefined minimum and maximum transaction response times that a related transaction can accept,

You can use this diagram to determine whether server performance is in an acceptable range.

WebResources (web resource analysis)
Web resource analysis is the performance analysis of Web servers starting from the server.

1, Hits per Second (click number of seconds)
Click per Second, even if the number of HTTP requests submitted to the Web server per second by the virtual user during the run scenario.
It enables you to evaluate the amount of load generated by a virtual user, such as comparing it to the average transaction response time graph,

You can view the impact of the number of clicks on transactional energy.

By viewing the "click per Second", you can determine whether the system is stable.

The decline in system clicks usually indicates that the response speed of the server is slowing down, and further analysis is needed to find the bottleneck of the system.

2, throughput (throughput rate)
Throughput shows the throughput per second of the server during the scenario run. Its unit of measure is byte,

Represents the amount of data that the virtual uses to obtain from the server in any given second.
The amount of load generated by the virtual user can be evaluated based on the throughput of the server.

And see the server's capacity to handle traffic and whether there are bottlenecks.
The difference between the throughput and CTR graphs:
The "CTR" chart is the number of HTTP requests processed by the server per second.
The throughput graph is the total amount of data that the client obtains from the server per second.

3. HTTP Status Code Summary (Overview of HTTP state codes)
The HTTP status Code profile shows the number of HTTP status codes returned from the Web server during a scene or session step, grouped by code. The HTTP status code represents the status of the HTTP request.

4, HTTP responses per Second (number of HTTP responses/sec)
The number of HTTP responses per second is to show the number of different HTTP status codes returned from the Web server per second in the course of the run scenario, as well as to return information on various status codes, which can be used to determine the operation of the server under pressure by analyzing the status code. You can also locate the code script that generated the error by grouping the results shown in the diagram.

5, Pages Downloader persecond (number of downloads per second)
Download pages per second shows the number of pages downloaded from the server in each second of the scene or session step.

Use this figure to calculate the amount of load generated by vuser based on the number of pages downloaded.
As with throughput graphs, the number of downloaded pages per second icon is the amount of data that VUser receives from the server in any given second. However, throughput is considered to be extremely large in each resource (for example, the size of each GIF file, the size of each page)

The number of pages downloaded per second takes into account only the number of pages.
Note: To see the download page map per second, you must set the number of pages per second (HTML mode only) in R-t-s.

6, retries per Second (number of retries/sec)
Retry per second shows how many times the server attempts to connect in each second of the scenario or session step.
The server connection will be retried in the following situations:
A, the initial connection is unauthorized
B, require proxy server authentication
C, the server shut down the initial connection
D, the initial connection could not connect to the server
E, the server initially failed to resolve the IP address of the load generator

7, Retries Summary (the summary of the number of retries)
The "Retry Count profile" shows how many times the server tried to connect during a scene or session step.

It is grouped by retry reason.

Use this diagram in conjunction with the Retry count chart per second to determine at what point in time the server was retried during a scenario or session step.

8, connections (connection number)
Number of connections displays the number of TCP/IP connections that were opened at each point in the run of the scene or session step.
With this figure, you know when you need to add a connection.
Example: When the number of connections reaches a steady state and the transaction response time increases rapidly, adding a connection can greatly improve performance (transaction response time will be reduced).

9, connections per Second (number of connections/sec)
The number of connections per second shows how many TCP/IP connections were established per second during the run.
Ideally, many HTTP requests should use the same connection instead of opening a new connection for each request.

By the number of connections per second graph can be seen server processing, indicating that the performance of the server is gradually declining.

10, SSLs per Second (number of SSL connections/sec)
SSL connections per second displays new and reused SSL that is opened in each second of a scenario or session step run

Number of connections. When you open a TCP/IP connection to a secure server, the browser opens the SSL connection.

Web page Breakdown (page element subdivision)
Page element segmentation is primarily used to evaluate whether page content affects the response time of a transaction.

It can be deeply analyzed on the site of those who download very slow graphics or interrupted connections and so on problematic
Elements.

1, Web page Breakdown (page decomposition of the total map)
Page splitting shows how a particular transaction responds to the test process, and then analyzes whether the related transaction is functioning properly.
The page decomposition diagram can be further subdivided in the following four ways:
1), Downloadtime breaddown (download time breakdown)
"Download Time Breakdown" diagram shows the download time of different elements in the Web page, but also can be in accordance with the download process to decompose time, with different colors to show the DNS resolution time, establish connection time, the first buffer time, and so on their respective proportions.
2), Componentbreakdown (Over time) (component subdivision (varies with the times))
The component breakdown diagram shows a breakdown of the page components of the selected page over time.

This diagram makes it easy to see which elements are not stable to download during the test.

This diagram is especially useful for pages that require more than the client to download controls, and by analyzing the control's response time, it is easy to see that those controls are unstable or time-consuming.
3), Downloadtime breakdown (Over time) (download time Breakdown (change over the Times))
The download time breakdown (varies over time) diagram shows the page element download time breakdown (over time) for the selected page, which shows very clearly how each element of the page is downloaded during the stress test.
The "Download Time Breakdown" diagram shows the results of a time statistic analysis of the response of page elements throughout the test process. Download time Breakdown (change over time) "What's displayed?" The statistical results of the response time of the page elements in each second of the scene running, both from the macroscopic and microscopic angles to analyze the download time of the page elements.
4), Timeto the breakdown (over time)

(First buffer time subdivision (varies over time))
The first buffer time breakdown (over time) figure shows that the first buffer returned from the Web server was successfully received

Before this time, the scene or session steps run every second of the server time and network time of each page component (

in seconds). You can use this diagram to determine when a scenario or session step is running when a server or network problem occurs.