Transaction Analysis content:
user transaction performance analysis is the basis of analysis performed from the user point of view.
1, Transation Sunmmary (transaction review)
on a comprehensive analysis of whether the transaction success and failure, the system determines the user transactions running in a certain test of time.
2, Average Transaciton Response Time (Average transaction response time)
average transaction execution time during a test run with the scenario, which can be analyzed by the performance of the system during the test to application scenario run.
3, Transactions per Second (transactions per second by)
every 1 second for each transaction by the scenario, the failure and the number of stops, the performance analysis TPS mainly to see the trend curve.
Example: When the pressure increased, CTR / TPS curve changes slowly or if there is a flat trend is likely to start the server bottleneck.
4, Total Transactions per Second (by the total number of transactions per second)
in the scene is running, the total number of transactions each second passed, failed to stop Affairs Department and the total number of transactions.
5, Transaction Performance Sunmmary (Transaction Performance Summary)
Transaction Performance Summary: Displays the minimum of all transactions, maximum and average execution time, response time can be directly determined whether the user's requirements.
6, Transaction Response Time Under Load (transaction response time and load)
"Transaction Response Time and load" combination "running virtual user" FIGS "average response transaction time" chart, through which can be seen at any point in time transaction response time relationship with the number of users, so that the user know the performance of data concurrency in the system to provide a reference for the expansion of the user's system.
Web Content Resource Analysis:
1, Hits per Second (clicks per second)
"Hits per Second", even running the scenario during the second virtual user submitted to the Web server's HTTP requests.
2, Throughput (throughput)
"throughput" is displayed per second throughput scenario during the operation of the server. Which is a unit of measure of bytes, each represents a virtual second used in any given
amount of data obtained from the server.
Can be assessed based on the throughput of server load virtual user-generated, and the processing power of the server to see in terms of traffic and the presence of bottlenecks.
3, HTTP Status Code Summary (HTTP status code Outline)
"Summary HTTP status code" shows the number of HTTP status codes scenario or session-step process is returned from the Web server,
the code is grouped according to FIG. HTTP status code represents the status of HTTP request similar to the following:
2xx - Success
3xx - Redirection
4xx - Client Error
500 - Internal Server Error. *
4, HTTP Responses per Second (HTTP Responses per second)
HTTP Responses per Second: HTTP status code is the number of different scenarios during operation of the second display is returned from the Web server,
but also other types of information returned status code, by analyzing the status code, the server can run at a determined pressure.
5, Pages Downloader per Second (number of pages downloaded per second)
download the number of pages per second: The number of pages within seconds of each downloaded from the server. Using this map may be calculated based on the number of pages downloaded Vuser load generated.
6, Retries per Second (retry number of times per second)
"Retry times per second" shows the number of connection attempts to each second scenario or session server running step.
In the following situations server connection is retried:
A, initial connection unauthorized
B, proxy authentication requires
C, the server closes initial connection
D, the initial connection to the server can not connect
E, the first server can not resolve the IP address of the load generator
7, Connections (connections)
Connections: Shows the number of TCP / IP connection or session scene during the step operation each time point opened. With this figure,
you can know when you need to add other connections.
8, Connections Per Second (connections per second)
connections per second: Shows the number of TCP / IP connection established during operation per second.
9, SSLs Per Second (SSL connections per second)
SSL connections per second: to display a new scene and the number of SSL connection or session running steps each second open reused.
When you open TCP / IP connection to a secure server, the browser will open an SSL connection.
Subdivision of page elements:
. 1, the Download Time Breaddown (download time division)
download time segments: FIG display page download time of the different elements, but can also download process in accordance with the decomposition time,
with different colors to display DNS resolution time, time to establish connection, the proportion of the first buffer each time.
2, Component Breakdown (Over Time) ( Component Breakdown (Over Time))
Component Breakdown: Breakdown graphs display the selected web page components over time. From this figure we can easily see which
element is unstable download time during the test.
3, Download Time Breakdown (Over Time ) ( Download Time Breakdown (time-varying))
Download Time Breakdown: The figure below shows the selected page elements page download time breakdown, it shows very clearly the various page
elements in pressure Download the case of the testing process.
4, Time to First Buffer Breakdown ( Over Time) ( First Buffer Breakdown (time-varying))
First Buffer Breakdown: Displays successfully received during this time period before the first Web server returns buffer ,
the server each time the page every second component scene or session and the step of running network time (in seconds).
This may be used to determine FIG scene or session of time steps during the operation of the server or network.
First Buffer Time: refers to the client to establish a connection with the server, the first packet transmission start time from the server,
the data through the network to the client, to the browser receives the first time a buffer used.
5, Page Component Breakdown (Page Component Breakdown)
Page Component Breakdown: graph displays the average download time (in seconds) for each web page and its components.
6, Page Component Breakdown (Over Time ) ( page exploded assembly (time-varying))
page exploded assembly (time-varying): graph displays the average response time per page and its components during each second pressure measurement operation ( in seconds).
7, Page Download Time Breakdown (Page Download Time Breakdown)
Page Download Time Breakdown: The figure below shows breakdown of each page component's download time can be determined according to its website during the download transaction response
time is caused by a slow network error or by the server error cause.
8, Page Download Time Breakdown (Over Time) ( page download time segments (time-varying))
page download time segments: the measured pressure during operation of the display, each page component segments of each second download time.
9, Time to First Buffer Breakdown (First Buffer Breakdown)
First Buffer Breakdown: display each successfully received within this period of time before the first buffer returned from a Web server
-related components of the page server / network time. If the download time component is very long, you can use this graph to determine issues arising from the
server related or related to the network.
Network Time: defined as the first HTTP request that moment, the average time that elapsed until confirmed.
Server Time: defined as from the receipt of the initial HTTP request confirmation begin until successfully received from the Web server of a buffer that elapsed between
the average time.
10, Downloader Component Size (KB) ( Downloaded Component Size)
Downloaded Component Size: display each page has been downloaded established size.