Latency measurement in resource requests
First Claim
1. A method comprising:
- providing, by a service provider, executable code for generating a set of requests to the service provider to determine latency information for different components of the service provider, wherein the executable code includes instructions for configuring a first request and a second request to determine latency information from the set of requests, wherein the first request is configured to be directed to a first identified component of the service provider at a first IP address and the second request is configured to be directed to a second identified component of the service provider at a second IP address, and wherein the first and second identified components of the service provider are different;
obtaining, by the service provider, the first and second requests from a client computing device at different components of the service provider, wherein each of the first and second requests is generated by the client computing device as a function of having executed the provided executable code and wherein the first request is obtained by the first identified component of the service provider and the second request is obtained by the second identified component of the service provider;
processing, by the service provider, the first and second requests to determine latency information, wherein the processing includes collecting information associated with the respective first and second requests to determine latency information; and
determining, by the service provider, latency information associated with the first and second requests from the client computing device, the latency information corresponding to a communication latency between the client computing device and the first and second identified components of the service provider.
1 Assignment
0 Petitions
Accused Products
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.
-
Citations
19 Claims
-
1. A method comprising:
-
providing, by a service provider, executable code for generating a set of requests to the service provider to determine latency information for different components of the service provider, wherein the executable code includes instructions for configuring a first request and a second request to determine latency information from the set of requests, wherein the first request is configured to be directed to a first identified component of the service provider at a first IP address and the second request is configured to be directed to a second identified component of the service provider at a second IP address, and wherein the first and second identified components of the service provider are different; obtaining, by the service provider, the first and second requests from a client computing device at different components of the service provider, wherein each of the first and second requests is generated by the client computing device as a function of having executed the provided executable code and wherein the first request is obtained by the first identified component of the service provider and the second request is obtained by the second identified component of the service provider; processing, by the service provider, the first and second requests to determine latency information, wherein the processing includes collecting information associated with the respective first and second requests to determine latency information; and determining, by the service provider, latency information associated with the first and second requests from the client computing device, the latency information corresponding to a communication latency between the client computing device and the first and second identified components of the service provider. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A computer-implemented system comprising:
-
a data store for storing performance metric information associated with processing resource requests; and a computing system in communication with said data store that is operative to; provide information for generating a series of requests to a service provider to determine latency information for different components of the service provider, wherein the information includes instructions for configuring at least a first request and a second request to determine latency information from the series of requests, wherein the first request is configured to be directed to a first identified component of the service provider at a first IP address and the second request is configured to be directed to a second identified component of the service provider at a second IP address, and wherein the first and second identified components of the service provider are different; obtain the first and second requests from a client computing device at different components of the service provider, wherein each of the first and second requests is generated by the client computing device having executed the provided instructions and wherein the first request is obtained by the first identified component of the service provider and the second request is obtained by the second identified component of the service provider; process the first and second requests to determine latency information, wherein the processing includes collecting information associated with the respective first and second requests to determine latency information; determine latency information associated with each of the first and second requests, 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; and update performance metric information according to the latency information. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A computer-implemented system comprising:
at least one processing device that is operative to; provide, by a service provider, executable code for generating a set of requests to the service provider to determine latency information for different components of the service provider, wherein the executable code includes instructions for configuring a first request a second request to determine latency information from the set of requests, wherein the first request is configured to be directed to a first identified component of the service provider at a first IP address and the second request is configured to be directed to a second identified component of the service provider at a second IP address, and wherein the first and second identified components of the service provider are different; obtain, by the service provider, the first and second requests from a client computing device at different components of the service, wherein each of the first and second requests is generated by the client computing device as a function of having executed the provided executable code and wherein the first request is obtained by the first identified component of the service provider and the second request is obtained by the second identified component of the service provider; process, by the service provider, the first and second requests to determine latency information, wherein the processing includes collecting information associated with the respective first and second requests to determine latency information; and determine, by the service provider, latency information associated with the first and second requests from the client computing device, the latency information corresponding to a communication latency between the client computing device and the first and second identified components of the service provider. - View Dependent Claims (16, 17, 18, 19)
Specification