KR101616063B1 - Content server latency determination - Google Patents

Abstract

The performance of the publisher server, the first content server, and the second content server is determined. The latency time information is determined based on the performance of the publisher server, the performance of the first content server, and the performance of the second content server, and the latency time information includes the latency time information of the publisher server, And represents the length of time for loading the content related to each of the servers.

Description

Content Server Latency Determination {CONTENT SERVER LATENCY DETERMINATION}

This specification relates to retrieval of information.

Content displayed on a web page may be generated by one or more content item servers in response to a content item request generated during rendering of a web page by a client device. A content item can be generated simultaneously with rendering of a web page. Likewise, the received content item in response to the content item request can be processed concurrently with respect to the rendering of the web page. For example, when a web page is rendered, JavaScript may execute and request an advertisement from a first content server. Again, the first content server may request an advertisement from the second content server. If the advertisement is searched concurrently, rendering of the web page is delayed until the requested advertisement is received from the content server. Once an advertisement is received and rendered and displayed, e.g., on a web page, rendering to the rest of the web page is resumed.

A drawback of simultaneous content item retrieval is that rendering of the rest of the web page will be delayed if the content item server is slow. To mitigate the potential impact of simultaneous content item processing, a Web page publisher identifies the cause of such a delay, i.e., a content item server that may be slow or temporarily incapable of execution, Time). However, it is a complex task to compile multiple HTTP requests and responses from a rendering of a web page in order to calculate the latency time associated with different servers in general. For example, multiple HTTP requests and responses may appear to be non-compliant because they do not appear in the web page itself, but are returned by the first content server. Further, when it is determined that a particular server, for example, the second content server, is the cause of the delay, it is difficult to prove the delay to the operator of the second content server.

According to some implementations, the capabilities of the publisher server, the first content server, and the second content server are determined. The latency time information is determined based on the performance of the publisher server, the performance of the first content server, and the performance of the second content server. The latency time information indicates a length of time for loading content related to each of the publisher server, the first content server, and the second content server.

According to some implementations, a URL (Uniform Resource Locator) of a document containing a reference to a script with a first behavior may be specified, where a first argument is appended to the URL do. The URL of the document containing the reference to the script having the second action may be specified, where the second argument is appended to the URL. The document containing the script is received in response to the request. The script with the first action is executed to determine the publisher server latency time, and the script with the second action is executed to determine the first content server latency time. The second content server latency time is determined based on the publisher server latency time and the first content server latency time.

According to some implementations, the system comprises a processor configurable to determine performance with respect to a publisher server, a first content server, and a second content server. Wherein the client device is configurable to determine latency time information based on the performance of the publisher server, the performance of the first content server, and the performance of the second content server, the latency time information including the latency time information, And a length of time for loading content linked to the server and the second content server, respectively. According to some implementations, a system includes a processor configurable to request content from one or more remote locations, wherein the content includes computer executable instructions for determining latency information regarding the request. An interface operably coupled to the processor is configurable to display the latency information and the latency information includes latency time for the one or more remote points associated with the indication of the content in the interface.

According to some implementations, content is requested, the request is a URL to the content, and the URL includes an appended argument. The requested content may be loaded into the content page in the first user interface. A second user interface may then be displayed. One or more content items associated with the content page may be subsequently displayed in the second user interface according to the factor added to the URL. In addition, one or more attributes relating to the one or more content items may be displayed in the second user interface.

According to some implementations, a first portion of a content page containing content received from a publisher server in a first user interface may be loaded. The second user interface may then be displayed. A second portion of the content page may be loaded in the second user interface and the second portion comprises one or more content items received from the one or more content servers. In addition, one or more attributes relating to the one or more content items may be displayed in the second user interface.

According to some implementations, the system includes a publisher server that is configurable to send a first portion of a content page containing the publisher content to a client device. Additionally, the one or more content servers may be configured to transmit a second portion of the content page containing the one or more content items to the client device. The client device loading the first portion of the content page in a first user interface and loading the second portion of the content page in a second user interface, Lt; RTI ID = 0.0 > and / or < / RTI >

According to some implementations, a system includes a client device that is configurable to store a copy of one or more content items associated with a content page received from one or more content servers. Additionally, the processor is configurable to generate a user interface, generate combined source code for the one or more stored content items, and insert the combined source code into the user interface.

According to some implementations, the system includes a publisher server that is configurable to capture one or more content item identifiers associated with one or more content items. The server processor is configurable to generate a user interface, generate a request for a content server requesting the one or more content items associated with the one or more content item identifiers, and provide the one or more content items in the user interface .

1 is a block diagram of an exemplary system for requesting content from a content server.
2 is an exemplary process for determining the latency contribution.
3 is another exemplary process for determining the latency contribution.
4 shows an exemplary interface for displaying the output of the NoFetch mode.
Figure 5 shows an exemplary interface for displaying the output of the NoRender mode.
Figure 6 is an exemplary process for determining the cause of a latency problem.
7 is an exemplary process for determining the latency time for one or more content servers.
8 is another exemplary process for determining the latency time for one or more content servers.
9 is another exemplary process for determining the latency time for one or more content servers.
10 is a drawing of an exemplary user interface.

1 is a block diagram of an exemplary system for requesting content from a content server. In one implementation, the content may include an advertisement, and the content server may be a content server. Different types of content may be requested.

In one implementation, the client system 100 is configured to view (e.g., visit a web page) content accessible over a network, e.g., the Internet. The client system 100 may be, for example, a web browser or a computing device executing network search software. The web address (e.g., URL) visited by the client system 100 may be analyzed to identify the publisher 102, e.g., the server hosting the corresponding web page.

In this example, the client system 100 may send a web page content request 104 to the publisher 102 for the web page content 106. In response to such a request, the publisher 102 provides the web page content 106 to the client system 100 as an HTML document containing, for example, JavaScript. Web page content 106 may include one or more content representations. In one implementation, the content indication may include an ad slot for an advertisement to be served by the content server. Other content displays are also available.

The web page content 106 provided by the publisher 102 includes a reference to a set of instructions 108. [ In one implementation, instruction 108 includes a store instruction 108a, a timing instruction 108b, and a request instruction 108c that are used to render and provide the requested content, e.g., an advertisement. In one implementation, the instruction 108 is provided by a first content server 134, e.g., a content server, and is stored in the client system 100, such as in a cache associated with a web browser.

Web page content 106 may define content slots 112-120 that are configured to display content from one or more content servers. In one implementation, content slots 112-120 are ad slots defined within an HTML tag. Instruction 108 generates a content request 122 to 130 that is generated to request content for populating content slots 112 to 120. [ In one implementation, such requests 122-130 are stored in a data store 132, such as buffer 132, and sent to content server 134 in one or more requests 136. [

In one implementation, the first content server 134 processes the received individual or combined request 136 and returns the identified content 138 to the client system 100. In another implementation, the first content server 134 processes the received individual or combined requests 136 from the client system 100 and sends the combined responses 137 to the client system 100. For example, the response may be HTML or JavaScript. The combined response 137 from the first content server 137 to the client system 100 causes the client system 100 to send one or more requests 140 to a second content server 142, To be transmitted. The second content server 142 may then return the identified content 144 to the client system 100, for example. The identified content 138 and / or 144 may then be displayed as part of the publisher's web page in a corresponding content slot, e.g., content slot 112, 114, and 116.

An example of the first content server 134 may include a Google ^TM content server. A request to populate the content slot on the web page with the advertisement may be made to the Google ^TM content server. Again, the Google ^TM content server may identify and provide an advertisement, or the Google ^TM content server may request an advertisement from the second content server 142, i.e., a third party content server. Although only two content servers 134 and 142 have been referred to, two or more content servers may provide content to a single web page.

When the client system 100 requests content from the publisher 102, the first content server 134 and / or the second content server 142 latency delay may occur. For example, the latency delay may be related to various problems such as slow network speed, slow publisher server 102, slow first content server 134, and / or slow second content server 142 . The user of the client system 100 may only know the total latency time that the web page takes to load. Therefore, it may be difficult to prove the determination of the latency delay contribution by the publisher server 102, the first content server 134, and the second content server 142.

As described in the above example, the total latency time L for displaying the web page is determined by the speed (L1) of the publisher server 102 including the speed of the network, the network latency time, The speed L2 and the speed L3 of the second content server 142. [ Thus, for example, an operation on the total latency time may be determined by L = L1 + L2 + L3.

Referring to FIG. 2, an exemplary process 200 for determining a latency contribution in accordance with some embodiments begins with determining the performance of the publisher server (step 202). In order to determine the performance of the publisher server 102, a request for content from the publisher server 102 may be made by including a factor (or other indicator) having the request. For example, the argument "google_nofetch" may be appended to the URL of a web page content point such as http://www.webpage.com?google_nofetch to implement the NoFetch mode.

A document associated with the requested URL may be received from the content point. The document may include web page content, media, text, downloadable files, and the like. The performance with respect to the publisher server 102, in other words, the latency time, can be determined. In some implementations, the content provision (e.g., JavaScript) tag within the web page content 106 implements the diagnostic logic. For example, the script file in the web page content 106 may generate information about the user interface by testing various conditions such as the latency time of the publisher server 102.

In the NoFetch mode, a script file in the web page content 106 may prevent a request to be made to the first content server 134 for a search for a content item from the first content server 134, i. For example, any request sent to the first content server 134 may be replaced with a NO-OP command to do nothing (except to generate a debug trace). Thus, execution in the NoFetch mode can set the reference performance for the publisher server 102 for the web page, i.e., the NoFetch latency time that the user will experience if the publisher does not add any advertisement to the web page.

Next, the performance of the first content server 134 is determined (step 204). In order to determine the performance of the first content server 134, an argument (or other indicator) may be included with the URL of the web page point. For example, the argument "google_norender" may be appended to the URL of a web page content point, such as http://www.webpage.com?google_norender, to implement NoRender mode.

In some implementations, the content provision (e.g., JavaScript) tag within the web page content 106 implements the diagnostic logic. For example, a script file in the web page content 106 may test various states such as performance with respect to the first content server 134, i.e., latency time, and create information about the user interface.

In the NoRender mode, the script file in the web page content 106 can return a content item from the first content server 134, i.e., a request to retrieve the ad can be sent to the first content server 134 have. However, after the first content server 134 retrieves the ad, the script file may prevent the ad from being rendered on the web page. For example, instead of rendering the actual ad on the web page in content slots 112, 114, and 116, the code associated with the ad in content slot 112, 114, and 116 is displayed. Therefore, it is possible to set the performance, i.e., the latency time, for the first content server 134 to search for an advertisement but not to render it, by executing the NoRender mode. The latency time of the first content server 134 can be calculated by subtracting the NoFetch latency time from the NoRender latency time, that is, L2 = NoRender latency time-NoFetch latency time L1.

In step 206, the performance of the second content server 142 may be determined. In order to determine the performance of the second content server 142, a request for the content from the first content server 134 requests a URL of the web page content point without arguments, such as http://www.webpage.com Lt; / RTI > The total page loading time associated with requesting and rendering the URL is equal to the total latency time (L). Therefore, the latency time associated with the second content server 134 can be calculated by subtracting the NoRender latency time from the total latency time, i.e., L3 = total latency time (L) - NoRender (L2).

After determining the performance of the publisher server, the first content server, and the second content server, the determination of the latency time information may be determined based on the publisher server performance, the first content server performance, and the second content server performance (step 208) . The latency time information may indicate a length of time for loading the content related to each of the publisher server, the first content server, and the second content server. For example, a user interface can be created, and information about the latency time that results in different components is created for that user interface. In some implementations, the user interface is created with JavaScript code that provides a separate browser window.

3 is another exemplary process 300 for determining the latency contribution. An exemplary process 300 for determining a latency contribution begins with presenting a URL to request a document containing a reference to the script, which includes a first factor added to the URL (e.g., Step 302). For example, the first argument "google_nofetch" may be appended to the URL for the web page content point, such as http://www.webpage.com?google_nofetch, to implement the NoFetch mode.

Next, the process 300 may present a URL for requesting a document containing a reference to the script, which includes a second argument added to the URL (step 304). For example, the argument "google_norender" may be appended to the URL of a web page content point, such as http://www.webpage.com?google_norender, to implement the NoRender mode.

In response to the request at steps 302 and 304, a document containing the script may be received (step 306). After receiving the document, the script may be executed to determine the publisher server latency time and the first content server latency time according to the first factor and the second factor (step 308). For example, the script may execute the NoFetch mode according to the first argument, and the script may execute the NoRender mode according to the second argument. Based on the publisher server latency time and the first content server latency time, the second content server latency time may be determined (step 310).

FIG. 4 shows an exemplary interface 400 for displaying the output of a script having a first operation to execute the NoFetch mode. Column 402 of FIG. 4 shows the latency time for the executed command in the NoFetch mode. For example, the latency time is expressed as an increasing execution time while executing the script. Column 404 of FIG. 4 provides a message type for the command being processed by the script executing the NoFetch mode. 4. Column 406 of FIG. 4 provides a summary message indicating the command being processed by the script executing the NoFetch mode. In the NoFetch mode, an executable script file in the web page content 106 may prevent retrieval of advertisements from one or more content servers. As indicated at 408 in FIG. 4, the script suppresses the fetching of the advertisements, so that the latency time information in the NoFetch mode can be associated with the publisher server.

After executing the script with the first action, a script with the second action may be executed to determine the first content server latency time (step 310). The script having the second action can execute the NoRender mode. 5 shows an exemplary interface 500 for displaying the output of the NoRender mode. Column 502 of FIG. 5 represents the latency time associated with the script executing the NoRender mode. For example, the latency time is expressed as the execution time that increases as you run the script. Column 504 of FIG. 5 provides a message type for the command being processed by the script executing the NoRender mode. Column 506 of FIG. 5 provides a summary message indicating the command being processed by the script executing the NoRender mode. Running the NoRender mode may set the performance that the first content server 134 searches for an advertisement but does not render it, as shown at 508 in FIG. The latency time for the first content server 134 can be calculated by subtracting the NoFetch latency time from the NoRender latency time, that is, L2 = NoRender latency time-NoFetch latency time L1.

After executing the document in the NoFetch and NoRender modes, the second content server latency time may be determined based on the publisher server latency time and the first content server latency time. In order to determine the performance of the second content server 134, a request for content from the first content server 134 may be sent to the publisher server 102 without arguments, such as the following http://www.webpage.com, By presenting the URL of the page content point. The total page loading time for requesting and rendering the URL is substantially equal to the total latency time L. Therefore, the latency time for the second content server 134 can be calculated by subtracting the NoRender latency time from the total latency time L, i.e., L3 = total latency time L - NoRender latency time L2 have.

6 is an exemplary process 600 for determining the cause of a latency effect. Based on the determination of the latency time for the publisher server, the first content server, and the second content server, the cause of the slow loading time associated with the content page can be determined. If L1 is determined to be slow in decision step 602, then the latency is likely due to the publisher server 102 (step 604). However, if L1 is determined to be fast in decision step 602, the present process 600 moves to decision step 606. [ In decision step 606, if L2 is determined to be slow, the cause of the latency is most likely due to the first content server 134 (step 608). If L2 is determined to be fast in decision step 606, the present process 600 moves to decision step 610. [ In decision step 610, if L3 is determined to be fast, the latency with the content page loading time may be considered slow (L1, L2 and L3 are all determined to be fast) (step 612). However, if L3 is determined to be slow in decision step 610, the cause of the latency is most likely to be due to the second content server 142 (step 614).

Based on the exemplary process described above, it can be determined that the most likely cause of the latency is due to the second content server 142. [ Based on this determination, an exemplary process 700 for determining the latency time associated with one or more content servers, such as second content server 142, is shown in FIG. First, the content may be requested, which is a URL to the content, which includes the appended arguments (step 702). The received content in response to such a request may be loaded into the content page of the first user interface (step 704). In one implementation, the content loaded into the content page may include a first portion of the content, and the first portion of the content includes only content from the publisher server 702.

Next, a second user interface may be displayed (step 706). To display a second user interface, a document containing a script may be requested, which includes an indicator. For example, the request may be a URL for receiving a document, and the indicator is an argument added to the URL. Such a document may then be received e.g. in response to the request. It is then possible to execute the script to display the second user interface in response to receipt of the indicator. For example, the second user interface may be a browser window separate from a browser window displaying a content page.

In other implementations, the first and second user interfaces may be displayed on the same interface. The first and second user interfaces may be rendered by a common browser on a common client device. For example, the first and second user interfaces may be rendered in a single user interface, such as a browser window running on the client device.

Then, one or more content items associated with the content page, e.g., an advertisement, may be displayed in the second user interface according to the factor added to the URL (step 708). In addition, one or more attributes for each content item of the second user interface may be displayed (step 710). For example, the displayed attribute may include a loading time and a total loading time for each content item.

In one implementation, displaying one or more content items may be accomplished by using a client-side implementation. For example, a copy of one or more content items to be inserted into the content item slot may be received from one or more content servers and stored. An onload callback may then be registered for the content page. During an on-load callback, a second user interface is displayed, and a scan is performed across the content item slots. After scanning across the content item slots, all of the code associated with the content item, such as HTML code, may be combined. This combined HTML code can then be inserted into the second user interface and all the content items can be created.

In another implementation, displaying one or more content items in a second user interface may be accomplished by using a server-side implementation. For example, one or more content item identifiers for one or more content items may be captured in JavaScript. A second user interface may then be opened, and a request for one or more content items may be made to one or more content servers by using one or more advertising identifiers. The one or more content items received from one or more content servers may then be rendered, for example, at a second user interface. In one implementation, the loading time for each content item may be displayed in a second user interface. In one implementation, the total loading time may be displayed at the second user interface.

In some implementations, the source code for the second user interface may be stored. For example, the user can browse and store the source code of the page in the second user interface. Storing the source code may be useful for proving the latency of one or more content items to an operator of the content server responsible for latency. In particular, the source code can be used to accurately pinpoint which content item, ie, the ad causes the greatest delay in loading time. For example, such source code may be emailed directly to an operator of the content server. Such source code may then be loaded in a user interface, such as a browser, to prove the latency with a particular content item.

Another exemplary process 800 for determining the latency time for one or more content servers, such as the second content server 142, is shown in FIG. After determining the cause of the latency associated with the content page, the first portion of the content page may be loaded in the first user interface, where the first portion includes content received from the publisher server (step 802). For example, a first portion of content may not include one or more content items from one or more content servers.

Next, a second user interface may be displayed (step 804). The source code, i.e. HTML code, for the second part of the content page may then be displayed in the second user interface, where the second part contains one or more content items received from one or more content servers (step 806 ). In a second user interface, a document containing a script may be requested to display source code associated with one or more content items, i.e., HTML code, and the request includes an indicator. For example, the request may be a URL for receiving a document, and the indicator is an argument added to the URL. The document may then be received e.g. in response to the request. It is then possible to execute the script to display the second user interface including the source code for one or more content items in response to receipt of the indicator.

For example, the argument "google_capture_norender" may be appended to the URL of the web page content point, such as http://www.webpage.com?google_capture_norender Accordingly, a second user interface including source code for one or more content items may be displayed. The source code may then be copied (step 808), pasted into the editor (step 810), and stored in the same file as the local HTML file (step 812). A user interface such as a browser or other user interface may then be used to open a file, such as a local HTML file, containing the source code for one or more content items (step 814). When opened, the file may render one or more content items associated with the content page in the user interface (step 816). In addition, one or more attributes for one or more content items may be displayed in the user interface (step 818). For example, the attribute may include a total loading time for one or more content items and a loading time for each content item.

9 is yet another exemplary process 900 for determining the latency time for one or more content servers, such as second content server 142. [ The process 900 begins by loading a first portion of a content page in a first user interface, wherein the first portion includes content received from a publisher server (Step 902). For example, a portion of a content page loaded with a first user interface may not include content from one or more content servers. Next, the second user interface is displayed (step 904). For example, the second user interface may be a window such as a pop-up window that is displayed in addition to the first user interface.

A second portion of the content page may then be displayed, e.g., at a second user interface, where the second portion includes one or more content items received from one or more content servers (step 906). In addition, one or more attributes relating to one or more content items may be displayed in a second user interface (step 908). For example, the attribute may include a total loading time for one or more content items and a loading time for each content item.

FIG. 10 is a drawing of an exemplary second user interface 1000 as described in the process. As indicated, one or more attributes relating to one or more content items may be displayed in the second user interface 1000. In one implementation, point and location information 1002 for each content item may be displayed in the second user interface 1000. [ In another implementation, the content item 1004 may be displayed in the second user interface 1000. In other implementations, the loading time 1006 for each advertisement may be displayed in the second user interface 1000. [ For example, an individual loading time 1006 may be associated with the advertisement 1004 displayed with the location and location information 1002. In other implementations, the total loading time 1006 may be displayed in the second user interface 1000. [

The apparatus, method, flowchart, and structural block diagrams described in this patent document may be implemented in a computer processing system including program code including program instructions executable by a computer processing system. Other implementations are available. Additionally, the flowcharts and structural block diagrams described in this patent document describe corresponding actions and / or specific methods supporting corresponding functions and steps supporting the disclosed structural means, corresponding software structures and algorithms, It can also be used to implement equivalents.

The description set forth herein provides an example for depicting the invention and enabling one of ordinary skill in the art to make and use the invention, and sets forth the best mode for the present invention. The description set forth herein is not intended to limit the invention to the exact conditions set forth. Thus, while the present invention has been described in detail with reference to the above examples, those skilled in the art will recognize that changes, modifications and variations may be made to the examples without departing from the scope of the invention.

Claims (40)

A computer-implemented content server latency determination method comprising:
Determining performance of the publisher server, wherein determining the performance of the publisher server comprises:
Sending a first request for a document from a client device to the publisher server, the document comprising one or more slots for displaying additional content to be received from one or more other content servers than the publisher server, , The document causing the client device to retrieve and render the additional content when executed by the client device in an operating mode and to cause the client device to retrieve and render the additional content when executed by the client device in a first diagnostic mode, Reference a script that prevents retrieval;
Receiving the requested document from the publisher server in response to the first request; And
Wherein the client device is configured to cause the client device to retrieve the document from the publisher server but to prevent the client device from retrieving the additional content. And executing by the client device the content server latency determination step. The method according to claim 1,
Wherein the performance of the publisher server comprises a request time for retrieving the document from the publisher server and a rendering time for rendering the document. The method according to claim 1,
Wherein executing the script in accordance with the first diagnostic mode to determine performance of the publisher server comprises:
Further comprising replacing content requests to the one or more content servers with non-content-request instructions. ≪ Desc / Clms Page number 21 > The method according to claim 1,
Wherein the transmitting the first request to the publisher server comprises:
Further comprising attaching an indicator to a Uniform Resource Locator (URL) requested in the first request, wherein the indicator specifies the first diagnostic mode How to determine server latency. The method according to claim 1,
Displaying a user interface; And
Further comprising displaying the performance of the publisher server in the user interface. The method of claim 5,
Wherein the step of displaying the performance of the publisher server comprises displaying the execution time information indicating the length of time for loading the content related to the publisher server on the user interface. Determination of latency. The method according to claim 1,
Determining a performance of a first content server that provides a reference to the additional content or the additional content. ≪ Desc / Clms Page number 21 > The method of claim 7,
Further comprising the step of determining a performance of a second, other content server to supply the requested content according to the reference provided by the first content server. The method of claim 8,
Determining latency time information based on the publisher server performance, the first content server performance, and the second content server performance, wherein the latency time information includes the latency time information, Wherein the content server server determines the content server latency by comparing the content server latency with the content server latency. The method of claim 7,
Wherein the first content server capability includes a first content search time for requesting and searching for a reference to content or content from the first content server. The method of claim 7,
The reference to the additional content refers to a second, other content server,
The script prevents a second search of the additional content from the second content server when executed in another diagnostic mode,
Wherein determining the performance of the first content server comprises:
Sending a second request for the document to the publisher server;
Receiving the document in response to the second request; And
And executing the script according to the second diagnostic mode to determine the first content server performance. The method of claim 8,
Wherein determining the performance of the second content server comprises:
Sending a third request for the document to the publisher server;
Receiving the document in response to the third request; And
And executing the script according to the operational mode to determine the second content server performance. A computer-implemented content server latency determination method comprising:
Sending, by a client device, three requests for a document identified by the URL to a publisher server, the document comprising one or more slots for displaying additional content to be retrieved from two or more content servers different from the publisher server Wherein the document includes a reference to a script and each request includes a no argument to be added to the URL, a first argument or a second argument, (1) an operation mode for causing the client device to search for the additional content from both the first and second content servers; (2) A first diagnostic mode for preventing retrieval of the additional content, and (3) And a second diagnostic mode for causing the client device to retrieve the additional content from the second content server but prevent the retrieval of the additional content by the client device from the second content server. To be executed by the client device;
Receiving the document in response to each of the three requests;
Executing, by the client device, the script in accordance with the first diagnostic mode to determine a publisher server latency time and in accordance with the second diagnostic mode to determine a first content server latency; And
And executing, by the client device, the script in accordance with the operation mode to determine a second content server latency time based on the publisher server latency time and the first content server latency time A computer implemented content server latency determination method. 14. The method of claim 13,
Further comprising displaying at least one of the publisher server latency time, the first content server latency time, and the second content server latency time in a user interface,
Wherein the user interface includes execution time information indicating a length of time for loading content associated with at least one of the publisher server, the first content server, and the second content server. How to determine server latency. 17. A content server latency determination system,
A processor configurable to determine performance with respect to a publisher server, a first content server, and a second content server; And
And a client device configurable to determine latency time information based on performance of the publisher server, performance of the first content server, and performance of the second content server,
Wherein the latency time information indicates a length of time for loading content associated with each of the publisher server, the first content server, and the second content server,
The processor
And transmits to the publisher server three requests for a document identified by the URL, the document comprising one or more slots for displaying additional content to be retrieved from two or more content servers different from the publisher server, Each request including a no argument, a first argument or a second argument to be appended to the URL, and the script including (1) a first argument, And (2) retrieving the additional content by the client device from each of the first and second content servers. (3) a first diagnostic mode for preventing the addition from the first content server to the client device In a mode of each of the three different modes, which is a second diagnostic mode that causes the client device to retrieve the additional content but prevents retrieval of the additional content by the client device from the second content server. ;
Receive the document in response to each of the three requests;
Execute, by the client device, the script in accordance with the first diagnostic mode to determine a publisher server latency time and in accordance with the second diagnostic mode to determine a first content server latency; And
Wherein the client device is configured to execute the script according to the operational mode to determine a second content server latency time based on the publisher server latency time and the first content server latency time. Latency determination system. The method of claim 8,
The first content server capability
A first advertisement request time for requesting advertisements from the first content server; And
And a second advertisement request time for requesting advertisements from the second content server. 16. The method of claim 15,
The client device may be further configured to display at least one of the capabilities of the publisher server, the performance of the first content server, and the performance of the second content server in a user interface,
Wherein the user interface includes execution time information indicating a length of time for loading content associated with at least one of the publisher server, the first content server, and the second content server. . 17. A content server latency determination system,
A client device including a processor coupled to a memory, the processor being configurable to execute instructions and perform operations,
Sending a first request for a document to a first remote location, the document comprising one or more slots for displaying additional content to be received from the first remote location and two or more other remote locations Wherein the client device is configured to cause the client device to search for and render the additional content when executed by the client device in an operational mode, and when executed by the client device in the first diagnostic mode, Reference a script that prevents retrieving the content;
Receiving the requested document as a publisher server in response to the first request; And
Wherein the client device is configured to cause the client device to retrieve the document from the publisher server but to prevent the client device from retrieving the additional content. The method comprising: And
An interface operably coupled to the processor and configured to display the determined publisher server performance. A computer-readable storage device having stored thereon instructions for causing a client device to perform operations when executed by a client device comprising a processor,
Determining a performance for a publisher server, the operation comprising:
Sending a first request for a document to the publisher server, the document comprising one or more slots for displaying additional content to be received from one or more other content servers than the publisher server, A script to cause the client device to retrieve and render the additional content when executed by the device in an operational mode and to prevent retrieval of the additional content by the client device when executed by the client device in a first diagnostic mode, Reference;
Receiving the requested document from the publisher server in response to the first request; And
Wherein the client device is configured to cause the client device to retrieve the document from the publisher server but to prevent the client device from retrieving the additional content. The computer program product comprising a computer readable storage medium having computer readable instructions thereon. 19. The method of claim 18,
Further comprising determining a performance of a first content server that provides a reference to the additional content or the additional content. A computer-implemented content server latency determination method comprising:
Receiving requests for advertisements from a client for each of a plurality of respective ad slots of a first web page;
Obtaining each command for each of a plurality of advertisements identified as a response to the requests; and causing each of the obtained commands to cause the client to display one of the advertisements when executed by the client;
Generating first instructions that, when executed by the client, cause the client to display each of the obtained instructions on the first web page without executing the obtained instructions;
Generating second instructions that, when executed by the client, causes the client to execute each of the obtained instructions to display each of the advertisements on a second web page according to a respective loading time; Is the latency caused by the content server for which the advertisement was requested; And
And sending the first and second instructions to the client in response to receiving the requests, wherein the first instructions, when executed by the client, cause the client to send each of the obtained instructions to the first web Page, so that the user of the client electronically provides a copy of at least a portion of each of the obtained instructions to a third party for review of the respective loading time. To determine a content server latency. 23. The method of claim 21,
Wherein the second instructions cause the client to further display a total load time on the second web page and the overall loading time is a loading time for all of the advertisements. To determine a content server latency. 23. The method of claim 21,
Further comprising receiving a request including an argument indicating that the first instructions will be displayed on the first web page. ≪ Desc / Clms Page number 22 > 24. The method of claim 23,
Further comprising providing the first instructions for display on the first web page. ≪ RTI ID = 0.0 > 31. < / RTI > 24. The method of claim 23,
Wherein the first instructions are Hypertext Markup Language (HTML). 24. The method of claim 23,
Wherein the first instructions are JavaScript (JAVASCRIPT). 23. The method of claim 21,
Wherein one of the received advertisements is identified by a content server. 17. A content server latency determination system,
One or more computers configured to perform operations,
Receiving requests for advertisements from a client for each of a plurality of respective ad slots of a first web page;
Obtaining each command for each of a plurality of advertisements identified as a response to the requests; and causing each of the obtained commands to cause the client to display one of the advertisements when executed by the client;
Generating first instructions that, when executed by the client, cause the client to display each of the obtained instructions on the first web page without executing each of the obtained instructions;
Generating second instructions that, when executed by the client, cause the client to execute each of the obtained instructions to display each of the advertisements on a second web page according to a respective loading time; Is the latency caused by the content server for which the advertisement was requested; And
And sending the first and second instructions to the client in response to receiving the requests, wherein the first instructions, when executed by the client, cause the client to send each of the obtained instructions to the first web Page so that the user of the client electronically provides a copy of at least a portion of each of the obtained instructions to a third party for review of the respective loading time. ≪ RTI ID = 0.0 > Decision system. 29. The method of claim 28,
Wherein the second instructions cause the client to further display a total load time on the second web page and the total loading time is a loading time for all of the advertisements. Decision system. 29. The method of claim 28,
Further comprising receiving a request including an argument indicating that the first instructions are to be displayed on the first web page. 32. The method of claim 30,
Further comprising providing the first instructions for display on the first web page. ≪ RTI ID = 0.0 > 31. < / RTI > 32. The method of claim 30,
Wherein the first instructions are Hypertext Markup Language (HTML). 32. The method of claim 30,
Wherein the first instructions are JavaScript (JAVASCRIPT). 29. The method of claim 28,
Wherein one of the received advertisements is identified by a content server. 23. The method of claim 21,
Wherein the first instructions include instructions for registering an onload callback for the first web page and the second web page is displayed during the onload callback. How to determine server latency. 36. The method of claim 35,
The second instructions, when executed by the client, cause the client to scan the ad slots, cause HTML code for each advertisement to be generated, and instruct the onload callback instructions to combine the generated HTML code Wherein the content server determines the content server latency. 37. The method of claim 36,
Wherein the onload callback is invoked when the first web page is loaded by the client. 23. The method of claim 21,
Wherein the advertisements are not displayed on the first web page. 29. The method of claim 28,
Wherein the first instructions include instructions for registering an onload callback for the first web page and the second web page is displayed during the onload callback. . 42. The method of claim 39,
The second instructions, when executed by the client, cause the client to scan the ad slots, cause HTML code for each advertisement to be generated, and instruct the onload callback instructions to combine the generated HTML code The content server latency determination system comprising :

Images