Adaptive accelerated application startup

• US 9,654,542 B2
• Filed: 06/09/2015
• Issued: 05/16/2017
• Est. Priority Date: 08/29/2008
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Roskind, James
• Primary Examiner(s): Huynh, Dung B
• Application Number:
  US14/734,040
• Publication Number:
  US 20150271246A1
• Time in Patent Office: 707 Days
• 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 comprising:

storing, by one or more applications running on at least one computing device, uniform resource locator (URL) hostnames in a memory of the at least one computing device and based on prior usage of the one or more applications by different users of the computing device; and

after initiation of entering activity by a user with the one or more applications and prior to completion of the entering activity with the one or more applications;

performing, by the one or more applications, asynchronous DNS pre-fetch resolutions for predicted hostnames and the stored URL hostnames, wherein the predicted hostnames are different than the stored URL hostnames;

receiving, by the one or more applications, resolution results for the predicted hostnames and stored URL hostnames in response to the performing step, the resolution results including a combination of pre-fetch information associated with the predicted hostnames and stored URL-hostnames;

discarding, from the resolution results, at least one IP address associated with at least one of the predicted hostnames or at least one of the stored URL hostnames; and

caching, by the one or more applications, the pre-fetch information for the received resolution results in a cache of the at least one computing device in preparation for a request of the predicted hostnames or stored URL hostnames.

2. The method of claim 1, wherein the pre-fetch information includes tracking information indicating whether a DNS task is at least one of queued, assigned and resolved.

3. The method of claim 1, wherein the pre-fetch information includes a central hashtable for hostnames and DNS resolution events.

4. The method of claim 1, wherein the pre-fetch information includes any of services relating to:

(i) enabling and disabling DNS pre-fetching, (ii) providing global entry points for DNS resolution requests, and (iii) monitoring and measuring performance of actual network stack resolutions required for web navigation.

5. The method of claim 1, wherein the stored hostnames are preprogrammed hostnames.

6. The method of claim 1, wherein the stored hostnames are generated by an application different from the one or more applications.

7. The method of claim 1, wherein the performing, receiving, and caching steps are performed by parallel threads of the application.

8. The method of claim 1, wherein the performing step further comprises:

inserting the predicted hostnames and stored URL hostnames into a work queue; and

performing a hostname-to-IP address DNS resolution or a next hostname in the work queue with an available work thread within a predetermined cache eviction time.

9. The method of claim 1, wherein the performing step includes making a DNS lookup call for the predicted hostname based on autocompletion logic or omnibox suggestions while a user is typing a hostname request and wherein the performing step is performed before the entering activity is completed.

10. The method of claim 1, wherein the storing step further comprises storing the URL hostnames based upon a number of first hostnames requested by the application following initial execution of an instance of the application.

11. The method of claim 1, wherein the storing includes avoiding storing of duplicate URL hostnames.

12. The method of claim 1, wherein the storing step further comprises storing the URL hostnames in a hostname queue based upon replaced values in link tags associated with the number of hostnames.

13. The method of claim 1, wherein the storing step further comprises storing the URL 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 one or more applications.

14. A system comprising:

a hostname storage device configured to store, by one or more applications, uniform resource locator (URL) hostnames in a memory of a computing device, and based on prior usage of the application by different users;

a DNS pre-fetcher integrated with the one or more applications and configured, after initiation of entering activity by a user with the one or more applications and prior to completion of the entering activity with the one or more applications, to;

perform asynchronous DNS pre-fetch resolutions for predicted hostnames and the stored URL hostnames, wherein the predicted hostnames are different than the stored URL hostnames;

receive resolution results for the predicted hostnames and stored URL hostnames in response to the performing step, the resolution results including a combination of pre-fetch information associated with the predicted hostnames and stored URL hostnames;

discard, from the resolutions results, at least one IP address associated with at least one of the predicted hostnames or at least one of the stored URL hostnames; and

cache the pre-fetch info on for the received resolution results in a cache of the computing device in preparation for a request of the predicted hostnames or stored URL hostnames.

15. The system claim 14, wherein the pre-fetch information includes tracking information indicating whether a DNS task is at least one of queued, assigned and resolved.

16. The system of claim 14, wherein the pre-fetch information includes a central hashtable for hostnames and DNS resolution events.

17. The system of claim 14, wherein the pre-fetch information includes any of services relating to:

(i) enabling and disabling DNS pre-fetching, (ii) providing global entry points for DNS resolution requests, and (iii) monitoring and measuring performance of actual network stack resolutions required for web navigation.

18. The system of claim 14, wherein the DNS pre-fetcher is further configured to make a DNS lookup call for the predicted hostname based on autocompletion logic or omnibox suggestions while a user is typing a hostname request and wherein the performing step is performed before the entering activity is completed.

19. A computer program product including a non-transitory computer-readable medium having instructions stored thereon that, if executed by a processing device, cause the processing device to perform operations comprising:

storing, by one or more applications, uniform resource locator (URL) hostnames in a memory of at least one computing device and based on prior usage of the application by different users of the at least one computing device; and

after initiation of entering activity by a user with the one or more applications and prior to completion of the entering activity with the application;

performing, by the one or more applications, asynchronous DNS pre-fetch resolutions for predicted hostnames and the stored URL hostnames, wherein the predicted hostnames are different than the stored URL hostnames;

receiving, by the one or more applications, resolution results for the predicted hostnames and stored URL hostnames in response to the performing step, the resolution results including a combination of pre-fetch information associated with the predicted hostnames and stored URL hostnames;

discarding, from the resolution results, at least one IP address associated with at least one of the predicted hostnames or at least one of the stored URL hostnames; and

caching, by the one or more applications, the pre-fetch information for the received resolution results in a cache of the at least one computing device in preparation for a request of the predicted hostnames or stored URL hostnames.