Method and apparatus for determining and using server performance metrics with domain name services

• US 8,195,831 B2
• Filed: 01/06/2011
• Issued: 06/05/2012
• Est. Priority Date: 07/19/2000
• Status: Expired due to Fees

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Swildens, Eric Sven-Johan, Day, Richard David, Gupta, Ajit K.
• Primary Examiner(s): Jean, Frantz
• Application Number:
  US12/986,055
• Publication Number:
  US 20110099290A1
• Time in Patent Office: 516 Days
• Field of Search: 709/235, 709/203, 709/234, 370/230.1, 370/229, 370/232
• US Class Current: 709/234
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 41/5083 wherein the managed service relates to web hosting
• CPC Class Codes: H04L 41/509 wherein the managed service relates to media content delivery, e.g. audio, video or TV
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4541 Directories for service discovery
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/101 based on network conditions
• CPC Class Codes: H04L 67/1027 Persistence of sessions during load balancing
• CPC Class Codes: H04L 67/1038 Load balancing arrangements to avoid a single path through a load balancer
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

Methods for determining and utilizing server performance metrics in a network are provided. For example, such methods can involve determining the service availability and metric measurements of types of services provided by a content delivery machine. User weightings can be used to indicate whether more traffic should be sent to one content server address compared to another. DNS servers use the test result updates and/or user weightings to determine the best server to return in response to a request to resolve a given DNS name. Computer systems and apparatus for carrying out such methods are also provided.

Claims

1. A process for determining and using server performance metrics in a network, comprising:

determining service availability and metric measurements of at least one service provided by a content server using a service metric probe resident on a server;

receiving one or more user weightings for traffic that indicate more traffic should be sent to one content server address compared to another content server address, wherein the traffic comprises client requests for web content;

determining, by a DNS server, in response to a request to resolve a given DNS name, a content server address to return, using updates to the service availability and metric measurements and the one or more user weightings, so as to cause client requests for web content to be directed to said determined content server address.

2. The process of claim 1, wherein the metric measurements comprise at least one metric selected from the group of:

CPU metric, memory metric, SNMP metric, network metric, and SCSI metric.

3. The process of claim 1, wherein the metric measurements comprise an overall load metric determined based on metrics reflecting a load on a content server.

4. The process of claim 1, wherein the at least one service includes any of:

HTTP, HTTPS, FTP, streaming media, and generic SNMP.

5. The process of claim 1, further comprising periodically performing metric tests on content servers within a service metric probe area, and wherein the service metric probe records metric results from the periodic tests.

6. A non-transitory computer program storage medium readable by a computer, tangibly embodying a program of instructions executable by a computer to perform steps for determining and using server performance metrics in a network, the steps comprising:

determining service availability and metric measurements of at least one service provided by a content server using a service metric probe resident on a server;

receiving one or more user weightings for traffic that indicate more traffic should be sent to one content server address compared to another content server address, wherein the traffic comprises client requests for web content;

determining, by a DNS server, in response to a request to resolve a given DNS name, a content server address to return, using updates to the service availability and metric measurements and the one or more user weightings, so as to cause client requests for web content to be directed to said determined content server address.

7. The non-transitory computer program storage medium of claim 6, wherein the metric measurements comprise at least one metric selected from the group of:

CPU metric, memory metric, SNMP metric, network metric, and SCSI metric.

8. The non-transitory computer program storage medium of claim 6, wherein the metric measurements comprise an overall load metric determined based on metrics reflecting a load on a content server.

9. The non-transitory computer program storage medium of claim 6, wherein the at least one service includes any of:

HTTP, HTTPS, FTP, streaming media, and generic SNMP.

10. The non-transitory computer program storage medium of claim 6, further comprising periodically performing metric tests on content servers within a service metric probe area, and wherein the service metric probe records metric results from the periodic tests.

11. A computer system for a determining and using server performance metrics in a network, comprising:

a service metric probe resident on a server that determines service availability and metric measurements of at least one service provided by a content server;

a user interface that receives one or more user weightings for traffic that indicate more traffic should be sent to one content server address compared to another content server address, wherein the traffic comprises client requests for web content;

a DNS server that, in response to a request to resolve a given DNS name, determines a content server address to return, using updates to the service availability and metric measurements and the one or more user weightings, so as to cause client requests for web content to be directed to said determined content server address.

12. The computer system of claim 11, wherein the metric measurements comprise at least one metric selected from the group of:

CPU metric, memory metric, SNMP metric, network metric, and SCSI metric.

13. The computer system of claim 11, wherein the metric measurements comprise an overall load metric determined based on metrics reflecting a load on a content server.

14. The computer system of claim 11, wherein the at least one service includes any of:

HTTP, HTTPS, FTP, streaming media, and generic SNMP.

15. The computer system of claim 11, wherein the service metric probe periodically performs metric tests on content servers within a service metric probe area, and wherein the service metric probe records metric results from the periodic tests.