Latency measurement in resource requests

• US 10,079,742 B1
• Filed: 09/15/2012
• Issued: 09/18/2018
• Est. Priority Date: 09/28/2010
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Richardson, David R., Cormie, John, MacCarthaigh, Colm, Redman, Benjamin W.S.
• Primary Examiner(s): Fan, Hua
• Application Number:
  US13/621,022
• Time in Patent Office: 2,194 Days
• Field of Search: 709218
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/101 based on network conditions
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Systems and method for the management and processing of resource requests by a service provider, such as a content delivery network (“CDN”) service provider, on behalf of a content provider are provided. The CDN service provider can measure the performance associated with the delivery of resources to a requesting client computing devices from various computing devices associated with the CDN service provider. In one embodiment, a client computing device can execute code, such as scripts, that cause the client computing device to transmit requests to different computing devices associated with the CDN service provider'"'"'s domain. Information associated with the processing of the responses can be used to measure CDN service provider latencies.

Claims

1. A computer-implemented method comprising:

obtaining, by a client computing device, a set of content for display on the client computing device, wherein the set of content includes executable code for causing the client computing device to generate a first request and a second request to a service provider to determine latency information for different components of the service provider, wherein the executable code includes an IP address associated with a point of presence (POP) of the service provider for receipt of individual requests, wherein the first and second requests are configured for transmission to different components of the service provider, and wherein the executable code further includes instructions for the client computing device to transmit the determined latency information to the service provider;

generating, by the client computing device, the first and second requests based on an execution of the executable code included in the set of content, wherein the first request is configured to be directed to a first IP address of a first component of the service provider and the second request is configured to be directed to a second IP address of a second component of the service provider, wherein the first and second components of the service provider are different; and

determining, by the client computing device, latency for each of the first and second requests, wherein the determining includes collecting information associated with the respective first and second requests to determine latency information, and wherein the latency information corresponds to a communication latency between the client computing device and the first and second identified components of the service provider respectively.

2. The method as recited in claim 1 further comprising transmitting the determined latencies from the client computing device to the service provider.

3. The method as recited in claim 1, wherein the second request is a request for a special resource, wherein the request for the special resource does not result in delivery of an actual resource to the client computing device.

4. The method as recited in claim 1, wherein the first request is not a request for a resource to be generated by the client computing device.

5. A computer-implemented system, the system comprising:

at least one client computing device that is operative to;

obtain a set of content for display on the at least one client computing device, wherein the set of content includes executable code for causing the at least one client computing device to generate a first request and a second request to a service provider to determine latency information for different components of the service provider, wherein the executable code includes an IP address associated with a point of presence (POP) of the service provider for receipt of individual requests, wherein the first and second requests are configured for transmission to different components of the service provider, and wherein the executable code further includes instructions for the client computing device to transmit the determined latency information to the service provider;

generate the first and second requests based on an execution of the executable code, wherein the first request is configured to be directed to a first IP address of a first component of the service provider and the second request is configured to be directed to a second IP address of a second component of the service provider, wherein the first and second components of the service provider are different; and

determine, at the at least one client computing device, latency for each of the first and second requests, wherein the determining includes collecting information associated with the respective first and second requests to determine latency information, and wherein the latency information corresponds to a communication latency between the client computing device and the first and second identified components of the service provider respectively.

6. The system as recited in claim 5, wherein the at least one client computing device is further operative to transmit the determined latencies from the client computing device to the service provider.

7. The system as recited in claim 5, wherein the second request identifies the same resource as the first request.

8. The system as recited in claim 5, wherein the first request is not a request for a resource to be transmitted by the service provider or for a resource to be generated by the client computing device.

9. A computer-implemented system, the system comprising:

a data store for storing performance metric information associated with processing content requests; and

at least one client computing device in communication with said data store that is operative to;

obtain a set of content for display on the at least one client computing device, wherein the set of content includes executable code for causing the at least one client computing device to generate a first request and a second request to a service provider to determine latency information for different components of the service provider, wherein the executable code includes an IP address associated with a point of presence (POP) of the service provider for receipt of individual requests, wherein the first and second requests are configured for transmission to different components of the service provider, and wherein the executable code further includes instructions for the client computing device to transmit the determined performance metric information to the service provider;

generate the first and second requests based on an execution of the executable code included in the set of content, wherein the first request is configured to be directed to a first IP address of a first component of the service provider and the second request is configured to be directed to a second IP address of a second component of the service provider, wherein the first and second components of the service provider are different; and

measure, by the at least one client computing device, latency information corresponding to processing the generated first and second requests at the client computing device, wherein the measuring includes collecting information associated with the respective first and second requests to determine latency information, and wherein the latency information corresponds to a communication latency between the client computing device and the first and second identified components of the service provider respectively.

10. The system as recited in claim 9, wherein the at least one client computing device is further operative to transmit, by the client computing device, the performance metric information corresponding to processing the generated first and second requests to the service provider.

11. The system as recited in claim 9, wherein the first request is not a request for a resource to be transmitted by the service provider or for a resource to be generated by the client computing device.