Adaptive Accelerated Application Startup

• US 20100057936A1
• Filed: 08/29/2008
• Published: 03/04/2010
• Est. Priority Date: 08/29/2008
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: ROSKIND, James
• Granted Patent: US 9,197,486 B2
• Time in Patent Office: Days
• US Class Current: 709/245
• CPC Class Codes: H04L 41/0293 for accessing web services by means of a binding identification of the management service or element
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

Embodiments of the present invention include methods and systems for accelerated application startup. A method for accelerating startup of an application is provided. The method includes persistently storing a number of uniform resource locator (URL) hostnames based on one or more hostname requests made by one or more users during use of the application. The method further includes, upon startup of the application, making a DNS lookup call for at least one of the stored hostnames prior to a hostname request initiated by the application, wherein a resolution result for at least one of the stored hostnames is cached in the operating system DNS cache in preparation for the hostname request. A system for accelerating startup of an application is provided. The system includes a hostname storage device, a DNS pre-fetcher and a startup DNS pre-cacher.

Claims

1. A method for accelerating startup of an application comprising:

persistently storing a number of uniform resource locator (URL) hostnames based on one or more hostname requests made by one or more users during use of the application;

upon startup of the application, making a DNS lookup call for at least one of the stored hostnames prior to a hostname request initiated by the application, wherein a resolution result for at least one of the stored hostnames is cached in the operating system DNS cache in preparation for the hostname request.

2. The method of claim 1, wherein at least one of the storing and making steps are performed by one or more parallel threads.

3. The method of claim 1, wherein the making step further comprises:

inserting the stored hostnames into a work queue; and

performing a DNS lookup call for a next hostname in the work queue with an available work thread.

4. The method of claim 1, wherein the storing step further comprises storing the number of hostnames based upon a number of most recent hostnames requested by one or more users during use of the application.

5. The method of claim 1, wherein the storing step further comprises storing the number of hostnames based upon a number of first hostnames requested by one or more users following startup of the application.

6. The method of claim 1, wherein the storing step further comprises storing the number of hostnames based upon a number of first hostnames requested by the application following startup of the application.

7. The method of claim 6, wherein one of the number of hostnames is a user'"'"'s home page.

8. The method of claim 1, wherein the storing step further comprises storing the number of hostnames based upon a number of most frequently requested hostnames by one or more users during use of the application.

9. The method of claim 1, wherein the storing step further comprises storing the number of hostnames based upon any combination of first hostnames following startup, most recent hostnames, or most frequent hostnames requested by one or more users during use of the application.

10. The method of claim 1, further comprising discarding at least one IP address provided by an operating system DNS resolver for the stored hostnames.

11. A method for accelerating startup of an application comprising:

receiving a number of stored uniform resource locator (URL) hostnames;

upon startup of the application, making a DNS lookup call for at least one of the stored hostnames prior to a hostname request initiated by the application; and

discarding at least one IP address provided by an operating system DNS resolver for the stored hostnames, wherein a resolution result for at least one of the stored hostnames is cached in the operating system DNS cache in preparation for the hostname request.

12. The method of claim 11, wherein the stored hostnames are preprogrammed hostnames.

13. The method of claim 11, wherein the stored hostnames are generated by another application.

14. A system for accelerating startup of an application comprising:

a hostname storage device configured to persistently store a number of uniform resource locator (URL) hostnames based on one or more hostname requests made by one or more users during use of the application;

a DNS pre-fetcher configured to make a DNS lookup call for at least one of the stored hostnames prior to a hostname request initiated by the application for any of the stored hostnames, wherein a resolution result for at least one of the stored hostnames is cached in the operating system DNS cache in preparation for the hostname request; and

a startup DNS pre-cacher configured to pass the number of hostnames to the DNS pre-fetcher from the hostname storage device upon startup of the application.

15. The system of claim 14, wherein at least one of the DNS pre-fetcher and the startup DNS pre-cacher are configured to perform tasks using one or more parallel threads.

16. The system of claim 14, wherein the startup DNS pre-cacher is further configured to store the number of hostnames based upon a number of most recent hostnames requested by one or more users during use of the application.

17. The system of claim 14, wherein the startup DNS pre-cacher is further configured to store the number of hostnames based upon a number of first hostnames requested by one or more users following startup of the application.

18. The system of claim 14, wherein the startup DNS pre-cacher is further configured to store the number of hostnames based upon a number of first hostnames requested by the application following startup of the application.

19. The system of claim 14, wherein the startup DNS pre-cacher is further configured to store the number of hostnames based upon a number of most frequently requested hostnames by one or more users during use of the application.

20. The system of claim 14, wherein the startup DNS pre-cacher is further configured to store the number of hostnames based upon any combination of first hostnames following startup, most recent hostnames, or most frequent hostnames requested by one or more users during use of the application.

21. The system of claim 14, wherein the DNS pre-fetcher is further configured to discard an IP address for at least one of the stored hostnames.