Interpreting Web page Diagnostics Web Subdivision diagram

Interpreting Web page Diagnostics Web Subdivision diagram

Http://blog.sina.com.cn/s/blog_62b8fc330100red5.html

Web Page Diagnostics (hereinafter referred to as WPD), this is a very important part of the LR analysis, to make it clear that this section of the content will let you take a lot less detours, many environmental problems can be through it to locate, such as the client, the network. Through it you can be better to locate the problem of the environment or the application itself, of course, more importantly, the Web page itself problems.

Web Page Diagnostics: Page diagnostic diagram, also called page decomposition General diagram

Page decomposition shows how a particular transaction responds to the test process, and then analyzes whether the related transaction is running properly.

The file structure under this view is broadly similar to a series of client requests such as Actions/transaction/web_url (or submit_form_request) in scripts, which is a three-tier architecture.

Transactions is the most basic unit that makes up the Web Page diagnostics view. The user can right-click on the transaction and then go to the Web page diagnostics for transaction interface to analyze the page under this transaction. Here are two points to note:

1) If the transaction structure has more than one level, such as Action/load_home_page, the user is allowed to enter only the child directory Load_home_page, even if the user selects the action system will automatically jump to the subordinate directory.

2) for a page request under a transaction, LR provides an operation that is either a break or a view page in Browser.

Because Web_url function is loads the specified Web page (GET request), there will be a request to return multiple times, the content returned from the server includes but not limited to HMTL, pictures, script files, and generated two request links.

For example, the request to open the Web Tours home page:

Web_url ("Webtours", "url=http://127.0.0.1:8080/webtours/", "resource=0", "reccontenttype=text/html", "Referer=", " Snapshot=t2.inf "," mode=html ", last);

The response obtained from the service side are:

http://127.0.0.1:8080/WebTours/

Http://127.0.0.1:8080/WebTours/welcome.pl?signOff=true

Http://127.0.0.1:8080/WebTours/images/hp_logo.png

Http://127.0.0.1:8080/WebTours/home.html

...

While submitting the login account Web_submit_form ("login111.pl",

"Snapshot=t3.inf",

ItemData,

"Name=username", "Value=zhutao", Enditem,

"Name=password", "Value=zhutao", Enditem,

"Name=login.x", "value=55", Enditem,

"Name=login.y", "value=3", Enditem,

last);

Although the URL address of the request is not explicitly specified here, it is also equivalent to sending a request to the server (login request), so the response can also be obtained from servers:

http://127.0.0.1:8080/WebTours/login.pl-note, a script library for handling customer requests, pl for Perl. If the Web site is using JavaScript, you need to download the script file with the suffix. js.

Http://127.0.0.1:8080/WebTours/login.pl?intro=true

Http://127.0.0.1:8080/WebTours/images/flights.gif

Http://127.0.0.1:8080/WebTours/images/signoff.gif

...

The Web Page Diagnostics View can be further subdivided in the following four ways:

Download time Breaddown (Download period breakdown)

Component breakdown (over time) (component breakdown (varies over times))

Download time Breakdown (Over time) (Download period breakdown (varies over times))

Time to primary buffer breakdown (over time) (first time breakdown of buffers (varies over times)

The Web page Diagnostics general diagram is based on transaction analysis, taking into account the preliminary analysis of the page.

The following seven charts are the further refinement of the Web page Diagnostics view, as can be seen from the name, is that the primary parsing object is the next level of the transaction-the page.

• Page Component Breakdown:

  Average response time for each element in the page as a percentage of the overall page response time

• Page Component Breakdown (Over time):

  During the entire test, the response time of each element of the page within any second (for example, the browser cache is set in runtime, the resource files on the page are only downloaded for the first time, and the subsequent page response times do not include the time of these elements, which is in page Component Breakdown is not visible because page Component breakdown is the average time during the entire test period. Of course, if the cache is enabled, you can see it through the over time graph)

• Page Download Time Breakdown: The response times split graph for each element in the page, the response time is divided into the following sections: DNS resolution,connection,first Buffer,ssl Handshaking,receive,ftp Authentication,client,error

• page Download Time breakdown: During the entire test process, the response times of each element in the page are divided by a graph

• Time to First Buffer breakdown: The first Buffer time is split into network time and server times, and the client HTTP request is sent to the server-side reply packet (ACK) to network time, from receive to ACK to complete first Buffer accepted as server time

• Time to First Buffer breakdown (Over time): Basic Ibid. in any second

• downloaded Component size (KB): size of each element in the page (KB)

Introduced so much, how to analyze it concretely?

First open the Web Page Diagnostics diagram and take a look at the following example download time graph:

There are two problems:

1, receive time is very long

This is generally a network problem, of course, if you confirm that the network is not a problem, then you have to look at the client is not a problem (the client may also cause the receive too long, this must be noted)

2, page problems

The page contains a lot of pictures, and the picture does not seem to be optimized, the biggest unexpectedly has 163K, write down, this is the evidence Oh;)

Many times, you can see if there is a network problem according to the dns,connection,receive, according to the client to determine whether there is a customer problem.

Look, it's quite simple! ^_^

Take a look, Page Component breakdown (over time)

It is clear that the page elements have been cache, indicating that the scene enabled the browser cache, the page response time only includes the red and blue lines.

Time to first Buffer breakdown, the diagram is not affixed, this diagram is very important, but also the most complex, where the value is not absolute, when the network condition is not good, the server time is likely to include network times, Because many page elements are smaller (less than 4k), the transfer is done in first buffer, so be sure to pay attention to the analysis.

Interpreting Web page Diagnostics Web Subdivision diagram