LoadRunner Learning---Web page Subdivision map Web page diagnostics

In the scene open the Diagnostics menu under the Web page diagnostics function, you can get the page analysis photos. Through this diagram, the composition of the transaction can be analyzed cobwebs, to get the analysis of each request time that makes up this page, and to further understand the distribution relationship between network and server processing time in response time. Through this function, can realize the front-end performance analysis of the website, clear the system response time is long by the server side (back-end) processing capacity is insufficient or short connection to the server network (front end) consumption caused.

1. Web page Diagnostics (Web page analysis)

Adding the graph will give you a list of pages that are accessed by the virtual user after the entire scene is run, which is the list of all page download times. Description (for analysis in registered user transactions, the entire payload consists of three page requests, one of which is always within a few seconds, while the other requests are longer and have an uptrend, and then the Select page to break The down command selects a specific page to obtain detailed information about each request

Download Time Analysis----can see the download time of the request and request that made up the operation. In this picture, we can focus on how much time is spent in the operation itself or when other factors such as page jumps are consumed.

Component time of each module-this function can be used to analyze whether the response time is longer because of slow page generation or because the picture resource is slow to download.

Download Time Module Download times--For each component of the time component that makes up the page element, it is convenient to confirm the processing time components of the element.

Time to Buffer--------Lists the time-allocation scale used by the element, which is more affected by network times or by the number of servers. Server time is how long the server is processing the page;

2.Page Download Time Breakdown (page response composition analysis)

Shows the composition analysis of each page response time, the response time of a page is generally composed of the following content:

The time the client will need to browse for the receive is not considered.

Connections time to connect to the server, the smaller the better.

DNS Resolution time required by DNS server to resolve domain names, resolution is affected by the DNS server, the smaller the better.

The error time server returns an incorrect response times, which reflects the speed at which the server is handling errors, typically returned directly by the Web server, containing the network time and the time the Web server returned an error, which is as small as possible.

First Buffer time is connected to the server, and the server returns the number of times it takes to return a byte, reflecting the cost of the system's processing time for normal requests, including network time and the server's normal processing time, which is as small as possible.

FTP Authentication time FTP authentication, this is the FTP login and other operations need to consume the authentication time, the shorter the better.

The time it takes to receive data, which reflects the size of the bandwidth, the greater the bandwidth, the shorter the download time.

SSL handshaking time SSL encryption handshake, and analysis here will analyze the composition of the page request graph, easy to analyze the page time wasted in which process.

3.Page Download Time Breakdown (page component times)

The response time varies over time for all requests to change the process. Each time component of each page in the entire load process is then made into a separate timeline to analyze how each request time that makes up the page at a different point in time changes. See most pages of the response time is relatively stable, where the first page refresh changes-the most obvious changes or the most responsive pages, and then on this page for further analysis to understand the time is too long or rapid changes in the cause.

4. Time to first Buffer breakdown (page request composition)

The scale of the page time request (client time/server time), through this graph, we can directly understand the entire page processing is on the server side of the long time spent, or the client spent a long time, so that the performance of the system to analyze whether the problem is in the front-end or in the back-end.

5, time-to-first Buffer breakdown (over times) (page-based request composition analysis)

During the entire load process, each requested server time and client times are trending along the way, and it is convenient to locate whether the response time changes over time due to changes in the client or due to server-side changes.

LoadRunner Learning---Web page Subdivision map Web page diagnostics