Asynchronous cache refresh for systems with a heavy load

• US 8,539,160 B2
• Filed: 09/10/2009
• Issued: 09/17/2013
• Est. Priority Date: 09/10/2009
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Gallagher, Stephen J.
• Primary Examiner(s): MACKALL, LARRY T
• Application Number:
  US12/556,887
• Publication Number:
  US 20110060881A1
• Time in Patent Office: 1,468 Days
• Field of Search: 711/133, 711/118, 711/E12.016
• US Class Current: 711/133
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

Abstract

A method and system to refresh a data entry in a cache before the data entry expires. The system includes a client computing system coupled to a server via a network connection. In response to a request for data access, the client computing system locates a data entry in a cache and determines whether the data entry in the cache has exceeded a refresh timeout since a last update of the data entry. If the data entry in the cache has exceeded the refresh timeout, the client computing system retrieves the data entry found in the cache in response to the request without waiting for the data entry to be refreshed, and requests a refresh of the data entry from the server via the network connection.

Claims

1. A method comprising:

locating, by a computing system, a data entry in a cache in response to a first request to access the data entry, wherein the cache has an expiration timeout that, when exceeded by an amount of time since a last update of a particular data entry, indicates that the particular data entry is to be updated before being provided, and wherein the cache has a refresh timeout that is shorter than the expiration timeout, and wherein when an amount of time since a last update of a particular data entry exceeds the refresh timeout but does not exceed the expiration timeout, the particular data entry can be provided once before being updated;

receiving by the computing system, at a particular time that occurs after the first request, a second request to access the data entry, wherein a difference between the particular time and a time at which the data entry was last updated exceeds the refresh timeout but does not exceed the expiration timeout;

in response to the second request, providing the data entry and transmitting a refresh request to refresh the data entry;

receiving by the computing system, after the transmitting of the refresh request but before the data entry has been refreshed, a third request to access the data entry; and

in response to the third request, providing the data entry after the data entry has been refreshed.

2. The method of claim 1, wherein the computing system comprises a Web server.

3. The method of claim 1, further comprising:

Indicating to an application that submits a request to access the data entry that the application can begin processing a next request without causing blocking of the next request.

4. The method of claim 1, further comprising:

in response to a determination that the data entry is not in the cache or is expired since the last update, retrieving data from a server to update the data entry in the cache.

5. The method of claim 4, wherein the server is one of a Lightweight Directory Access Protocol (LDAP) server, an NIS server, an NIS+ server, or an SQL database server.

6. The method of claim 1, further comprising:

queuing one of a plurality of refresh requests of a data entry; and

attaching information to the queued refresh request to indicate which requesting applications are requesting the data entry.

7. A non-transitory computer readable storage medium including instructions that, when executed by a computing system, cause the computing system to perform operations comprising:

locating, by the computing system, a data entry in a cache in response to a first request to access the data entry, wherein the cache has an expiration timeout that, when exceeded by an amount of time since a last update of a particular data entry, indicates that the particular data entry is to be updated before being provided, and wherein the cache has a refresh timeout that is shorter than the expiration timeout, and wherein when an amount of time since a last update of a particular data entry exceeds the refresh timeout but does not exceed the expiration timeout, the particular data entry can be provided once before being updated;

receiving by the computing system, at a particular time that occurs after the first request, a second request to access the data entry, wherein a difference between the particular time and a time at which the data entry was last updated exceeds the refresh timeout but does not exceed the expiration timeout;

in response to the second request, providing the data entry and transmitting a refresh request to refresh the data entry;

receiving by the computing system, after the transmitting of the refresh request but before the data entry has been refreshed, a third request to access the data entry; and

in response to the third request, providing the data entry after the data entry has been refreshed.

8. The non-transitory computer readable storage medium of claim 7, wherein the cache is locally coupled to the computing system.

9. The non-transitory computer readable storage medium of claim 7, wherein the operations further comprise:

Indicating to an application that submits a request to access the data entry that the application can begin processing a next request without causing blocking of the next request.

10. The non-transitory computer readable storage medium of claim 7, wherein the operations further comprise:

in response to a determination that the data entry is not in the cache or is expired since the last update, retrieving data from a server to update the data entry in the cache.

11. The non-transitory computer readable storage medium of claim 10, wherein the server is one of a Lightweight Directory Access Protocol (LDAP) server, an NIS server, an NIS+ server, or an SQL database server.

12. The non-transitory computer readable storage medium of claim 7, wherein the operations further comprise:

queuing only one of a plurality of refresh requests of a data entry; and

attaching information to the queued refresh request to indicate which requesting applications are requesting the data entry.

13. A system comprising:

a network interface device; and

a processor to;

receive, via the network interface device, a first request to access a data entry in a cache, wherein the cache has an expiration timeout that, when exceeded by an amount of time since a last update of a particular data entry, indicates that the particular data entry is to be updated before being provided, and wherein the cache has a refresh timeout that is shorter than the expiration timeout, and wherein when an amount of time since a last update of a particular data entry exceeds the refresh timeout but does not exceed the expiration timeout, the particular data entry can be provided once before being updated,

locate the data entry in the cache,

receive via the network interface device, at a particular time that occurs after the first request, a second request to access the data entry, wherein a difference between the particular time and a time at which the data entry was last updated exceeds the refresh timeout but does not exceed the expiration timeout,

in response to the second request, provide the data entry and transmit a refresh request to refresh the data entry,

receive via the network interface device, after the transmitting of the refresh request but before the data entry has been refreshed, a third request to access the data entry, and

in response to the third request, provide the data entry after the data entry has been refreshed.

14. The system of claim 13 further comprising the cache.

15. The system of claim 13, wherein the processor is also to retrieve data from a server to update the data entry in the cache, and wherein the server is one of a Lightweight Directory Access Protocol (LDAP) server, an NIS server, an NIS+ server, or an SQL database server.

16. The system of claim 13, further comprising:

a queue to enqueue one of a plurality of refresh requests of a data entry.

17. The system of claim 13, wherein the refresh timeout has a first value for a first category of data entries, and a second value for a second category of data entries.