http://www.51testing.com/html/10/325010-243603.html
Transactions (user transaction analysis)
User transaction analysis is the basic performance analysis from the user's point of view.
1. Transaction Sunmmary Comprehensive analysis
of transactions is the first step in performance analysis. By analyzing the success and failure of user transactions during the test period, you can directly determine whether the system is running normally.
2. Average Transaciton Response Time
The “Average Transaction Response Time” shows the average time taken for transaction execution in every second during the running of the test scenario, through which you can analyze the performance trend of the application system during the running of the test scenario .
Example: With the change of the test time, the speed of the system processing transactions begins to gradually slow down, which means that the overall performance of the application system will have a downward trend with the change of the production time.
3. Transactions per Second (transactions per second/TPS)
"Transactions per second/TPS" displays the number of passes, failures and stops of each transaction in every second of the scenario running, making it a useful tool for examining system performance. Important parameters. It is used to determine the time transaction load of the system at any given moment. Analysis of TPS is mainly to see the performance trend of the curve.
Comparing this to the average transaction response time allows you to analyze the effect of the number of transactions on execution time.
Example: When the pressure increases, if the CTR/TPS curve changes slowly or has a flat trend, it is very likely that the server starts to have a bottleneck.
4. Total Transactions per Second (Total transactions per second)
"Total transactions per second" displays the total number of transactions passed, failed transactions and stopped transactions in each second when the scenario is running.
5. Transaction Performance Sunmmary (transaction performance summary)
"Transaction performance summary" shows the minimum, maximum and average execution time of all transactions in the program, which can directly determine whether the response time meets the user's requirements.
Focus on the average and maximum execution time of the transaction, if the range is not within the acceptable time range for the user, a cause analysis is required.
6. Transaction Response Time Under Load (Transaction Response Time and Load)
"Transaction Response Time and Load" is a combination of the "Running Virtual User" graph and the "Average Response Transaction Time" graph, through which it can be seen that at any point in time The relationship between the transaction response time and the number of users, so as to grasp the performance data of the system in terms of user concurrency, and provide a reference for expanding the user system. This graph allows you to see the overall impact of virtual user load on execution time and is useful for analyzing test scenarios with ramping loads.
7. Transaction Response Time (Percentile) (Transaction Response Time (Percentile)) "Transaction Response Time (Percentile)" is a comprehensive analysis chart obtained by analyzing the
test results , that is, the chart obtained indirectly by the tool through some statistical analysis methods. It allows you to analyze the percentage of transactions that can be executed within a given transaction response time frame.
8. Transaction Response Time (Distribution)
"Transaction Response Time (Distribution)" shows the distribution of the time spent in transaction execution during the scenario running process, through which you can understand transactions with different response times during the test process quantity. If the system predefines the minimum and maximum acceptable transaction response times for the transactions in question, you can use this graph to determine whether server performance is within acceptable limits.
Web Resources (Web resource analysis)
Web resource analysis is the performance analysis of the Web server starting from the server.
1. Hits per Second (Hits per Second)
"Hits per second", even the number of HTTP requests submitted by virtual users to the Web server per second during the running scenario.
It allows you to assess the amount of load generated by virtual users, such as comparing it to the "Average Transaction Response Time" graph, to see the impact of hits on transaction performance. By checking the "number of clicks per second", you can judge whether the system is stable. A drop in the system hit rate 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)
"Throughput" shows the server's throughput per second during the scenario operation. Its unit of measurement is bytes, which represents the amount of data obtained from the server in any given second.
You can evaluate the load generated by virtual users based on the throughput of the server, as well as see the processing capacity of the server in terms of traffic and whether there are bottlenecks.
The difference between the "throughput rate" graph and the "click rate" graph:
The "throughput rate" graph is the number of HTTP requests processed by the server per second.
The "hit rate" graph is the total amount of data the client gets from the server per second.
3. HTTP Status Code Summary
"HTTP Status Code Summary" displays the number of HTTP status codes returned from the web server during a scenario or session step, grouped by code. HTTP status codes indicate the status of the HTTP request.
4. HTTP Responses per Second (HTTP responses per second)
"HTTP responses per second" is to display the number of different HTTP status codes returned from the Web server per second during the running scenario, as well as other types of status codes. , by analyzing the status code, you can judge the operation of the server under pressure, and you can also group the results displayed in the figure to locate the code script that generates the error.
5. Pages Downloader per Second
"Pages Downloader per Second" displays the number of web pages downloaded from the server in each second that the scenario or session step runs. Use this graph to calculate the amount of load generated by Vusers based on the number of pages downloaded.
As with the Throughput graph, the Pages Downloads per Second icon is the amount of data a Vuser receives from the server in any given second. But the individual resources considered for throughput are extremely small (eg, the size of each GIF file, the size of each web page). While the number of pages downloaded per second only considers the number of pages.
Note: To view the number of pages downloaded per second graph, you must set "Pages per second (HTML mode only)" in RTS.
6. Retries per Second
"Retries per second" shows the number of connections attempted by the server in each second that the scenario or session step runs.
The server connection will be retried in the following situations:
A. The initial connection is unauthorized
B. Proxy authentication is required
C. The server closes the initial connection
D. The initial connection fails to reach the server
E. The server was initially unable to resolve the IP address of the load generator
7. Retries Summary
The "Retries Summary" displays the number of connections attempted by the server during a scenario or session step run, grouped by reason for retries. Use this graph in conjunction with the retries per second graph to determine at what point during a scenario or session step the server retried.
8. Connections
"Connections" displays the number of TCP/IP connections opened at each point in time during the running of the scene or session step.
With the help of this graph, you can know when you need to add additional connections.
Example: When the number of connections reaches a steady state and the transaction response time increases rapidly, adding connections can greatly improve performance (transaction response time will decrease).
9. Connections Per Second "Connections
per second" displays the number of TCP/IP connections established per second during the running of the program.
Ideally, many HTTP requests should use the same connection, rather than opening a new connection for each request. Through the number of connections per second graph, you can see the processing of the server, indicating that the performance of the server is gradually declining.
10. SSLs Per Second
"SSL connections per second" shows the number of new and reused SSL connections opened within each second of the scenario or session step running. When a TCP/IP connection is opened to a secure server, the browser will open an SSL connection.
Web Page Breakdown (Web Page Element Breakdown)
"Web Page Element Breakdown" is mainly used to evaluate whether the page content affects the response time of the transaction. Through it, it can deeply analyze the problems such as slow download graphics or broken connections on the website.
element.
1. Web Page Breakdown (Page Breakdown)
"Page Breakdown" shows the response of a specific transaction in the testing process, and then analyzes whether the related transaction is running normally.
The "Page Breakdown" graph can be further subdivided in the following four ways:
1), Download Time Breaddown (Download Time Breakdown)
The "Download Time Breakdown" graph displays the download time of different elements in the web page, and can also follow the download process. The time is broken down, and different colors are used to display the respective proportions of DNS resolution time, connection establishment time, and first buffer time.
2), Component Breakdown (Over Time) (component breakdown (over time))
"Component Breakdown" graph displays the breakdown of the page components of the selected web page over time. This graph makes it easy to see which elements have unstable download times during testing. This graph is especially suitable for pages that need to download a lot of controls on the client side. By analyzing the response time of the controls, it is easy to find those controls that are unstable or time-consuming.
3), Download Time Breakdown (Over Time) (Download Time Breakdown (Over Time))
"Download Time Breakdown (Over Time)" The figure shows the download time breakdown (over time) of the page elements of the selected web page , which very clearly shows the download of each element of the page during the stress test.
The "Download Time Breakdown" graph shows the time statistical analysis results of page element response during the entire test process, and the "Download Time Breakdown (Varies with Time)" shows the statistics of page element response time in every second during the running of the scenario. As a result, the two analyze the download time of page elements from a macro and micro perspective, respectively.
4), Time to First Buffer Breakdown (Over Time) (the first buffer time subdivision (change with time))
The "First Buffer Time Breakdown (vs. Time)" graph shows the time before the successful receipt of the first buffer from the web server, for each second that the scenario or session step is run by the server for each web component time and network time in seconds. You can use this graph to identify when a server or network problem occurs during a scenario or session step run.
First Buffer Time: refers to the time from when the server sends the first data packet, the data is transmitted to the client through the network, and the browser receives the first buffer after the connection is established between the client and the server.
2. Page Component Breakdown
The "Page Component Breakdown" graph shows the average download time (in seconds) for each web page and its components. The graph column can be sorted by the average number of seconds it took to download components, which helps isolate problematic components.
3. Page Component Breakdown (Over Time)
The "Page Component Breakdown (Over Time)" graph shows the average response time of each web page and its components in every second during the program's operation (in seconds).
4. Page Download Time Breakdown
The "Page Download Time Breakdown" graph shows a breakdown of the download time of each page component and can be used to determine whether slow transaction response times during page downloads are caused by network errors or Caused by a server error.
The Page Download Time Breakdown graph breaks down the download process for each component based on DNS resolution time, connect time, first buffer time, SSL handshake time, receive time, FTP verification time, client time, and error time .
5. Page Download Time Breakdown (Over Time) (Page Download Time Breakdown (Over Time))
The "Page Download Time Breakdown (Over Time)" graph shows the download time of each page component in every second during the running of the scheme subdivision. Use this graph to determine at what point during a scenario a problem occurred with the network or server.
The Page Component Breakdown (over time) graph and the Page Download Time Breakdown (over time) graph are often combined for analysis: first identify the components in question, then analyze their download process to locate the cause in where.
6. Time to First Buffer Breakdown The
"First Buffer Breakdown" graph shows each page component during the period before the first buffer returned from the web server was successfully received relative server/network time. If a component takes a long time to download, you can use this graph to determine whether the problem is server- or network-related.
Network time: defined as the average time elapsed from the moment of the first HTTP request until the confirmation.
Server Time: Defined as the average time that elapses from the time the initial HTTP request acknowledgment is received until the successful receipt of a buffer from the web server.
7. Time to First Buffer Breakdown (Over Time) The server time and network time of each web component for each second of the scenario run during the period before a buffer. You can use this graph to identify the point in time during a scenario run that a problem occurs with the server or network.
8. Downloader Component Size (KB) (downloaded component size)
The "Downloaded Component Size" figure shows the size of each downloaded web page component. It can directly see which components are large and need further optimization to improve performance.