LR Real-Discuz Open Source Forum--Analysis of Web page subdivision results (Web page diagnostics)

The Discuz Open Source Forum project, which has been the creation of virtual user scripts (Generator) and scenes (controllers), has now finally reached the LoadRunner Performance test results Analysis section.

LoadRunner One of the most important charts in the analysis chart function is the Web diagnostic subdivision , which needs to be set in the menu bar before the Controller scene is designed to run the Web Diagnostics feature (diagnostic - Web Diagnostics - start),

A Web page subdivision is a display of the relevant download time and size for each page and its components, primarily to assess whether the page content affects transaction response time (only related to transaction response time). By associating with different transaction graphs, you can analyze the causes of slow or interrupted Web site downloads to determine if system performance issues are occurring on the network or the server, and then further analyze which web page or factors are causing the problem?

The following are the features of each chart of the page breakdown chart:

Page Breakdown chart, a total of8chart, which is the total page decomposition graph (Web pageDiagnostics), page Component Breakdown chart (page comporment Breakdown), Page component subdivision (change over time) (pageComportment breakdown over time), page download time breakdown chart (page Download Time breakdown), page download time breakdown (change over time) (page Download time breakdown over time), the first Buffer time subdivision chart (Time to first buffer breakdown), the first Buffer time subdivision (change over time) (Time to first buffer Breaddown over time), downloaded component size map(Downloaded Component Size) [KB].

1. Page Component Breakdown Chart: Displays the average download time (in seconds) of each page and its components, viewing which element in the selected page takes up the longest average download time.

2, the Page Component subdivision chart (change over time): This figure is suitable for page analysis when the client downloads more components, and by analyzing the download time to find out which components are unstable or time-consuming, it changes with the whole scene.

3. Page download Time Breakdown chart: Page download time breakdown chart based on DNS resolution time, connection time, first buffer time,SSL handshake time, receive time,FTP The validation time, client time, and error time are analyzed for each component. It can confirm that the slow response time is caused by a network error or by a server error during the Web page download period.

4, page download time breakdown chart (change over time): Displays the selected page download time breakdown, from which you can see each element of the page in the stress test process download. If a page is slow to open, by analyzing this graph, you can clearly see where the time to open the page is primarily, optimized for this issue.

5, the first buffer time subdivision diagram: Refers to the period of time before the first buffer returned from the Web server, the relevant server and network time of each page component (in seconds), which is important to analyze the time of the page, where the network time is from the first The average time that the HTTP request has elapsed until the confirmation is received. Server time is the average elapsed time from receipt of the initial HTTP request acknowledgement until the first buffer from the Web server is received successfully .

6, the first Buffer time subdivision chart (change over time): The first buffer time is after the client and the server to establish a connection, send the first packet from the server to start the time, the data after the network to the client, and then the browser to receive the first buffer data spent. (in the figure, it is useful to distinguish between the time spent by the server and the network in two colors to confirm that it is a server problem or a network problem!) ）

By understanding the above diagram, you can follow your own ideas to further analyze the length of time in the Web page, where the problem occurs

Let's share the following: I use these web-based subdivision charts to analyze test results.

Can you think,loadrunner Chart Analysis so much, analysis of ideas, steps from where to start ah? Don't worry!

My personal habits, the entire LR Results Analysis steps:

Results Summary --"Concurrency number analysis "--"response time --" hits per second –"Business success rate -- "System resources -- "Page subdivision map -- " Web Server Resources -- "Database Server

Here only the page subdivision of the idea of further analysis to comb, some figures are only for reference, do not need further analysis.

1, first open the page Decomposition General diagram (Web page diagnostics), on the left breakdown Tree , lists all the transaction names added in the script, usually, Our main focus is on the system business segment that needs to be concurrent , to look at the login section, which iscaused by two pages in the download time (Download), where The Receive section takes the longest time. (Component part is not seen here, because it is not intuitive here)

2, then open the Page Component Subdivision (page Component breakdown), to find out which element in the selected page of the average download time is more, in fact, the above two, but here is a pie chart to show more intuitive.

3. Then open the page download time Breakdown chart (page Download times breakdown), based on DNS resolution time, connection time, first buffer time,SSL handshake time, receive time, the distribution of the FTP authentication time, the client time, and the error time on the selected page determines whether the long response time for this page is caused by a network error or a server error , 1, Receive Time is the longest, the initial judgment is caused by network problems, but also may be a browser request problem, and then see the page download subdivision over time distribution figure 2, the entire login The page element has been downloaded in the scene? This is most likely a network problem. Another point, if the page cache is done well, it will not always download it.

Figure 1

Figure 2

4, finally open a very important diagram, that is, the first Buffer time subdivision (breakdown), the first Buffer time subdivision chart to compare the results are consistent, Because the first buffer time subdivision chart can also determine whether the page's response time is caused by a network error or a server error. From this graph, you can see that most of the time is in the network.

LR Real-Discuz Open Source Forum--Analysis of Web page subdivision results (Web page diagnostics)