Cache management

• US 10,198,462 B2
• Filed: 04/05/2012
• Issued: 02/05/2019
• Est. Priority Date: 04/05/2012
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Bose, Miko Arnab Sakhya Singha, Clarke, Simon, Oliver, David Charles, Malaczek, Malgorzata Anna
• Primary Examiner(s): Lazaro, David R
• Assistant Examiner(s): Henry, Mariegeorges A
• Application Number:
  US13/439,873
• Publication Number:
  US 20130268614A1
• Time in Patent Office: 2,497 Days
• Field of Search: 709213, 709217, 709219
• CPC Class Codes: G06F 15/167 using a common memory, e.g. mailbox
• CPC Class Codes: G06F 16/2255 Hash tables
• CPC Class Codes: G06F 16/24552 Database cache management

Abstract

Concepts and technologies are described herein for cache management. In accordance with the concepts and technologies disclosed herein, the server computer can be configured to communicate with a client device configured to execute a cache module to maintain a cache storing data downloaded from and/or uploaded to the server computer by the client device. The server computer can be configured to receive requests for data stored at the server computer. The server computer can be configured to respond to the request with hashes that correspond to the requested data. The client device can search the cache for the hashes, obtain the data from the cache if the hashes are found, and/or download the data from the server computer if the hashes are not found. The client device also can be configured to update the cache upon uploading the data to the server computer.

Claims

1. A computer-implemented method for managing a cache, the computer-implemented method comprising performing computer-implemented operations at a client device for:

receiving, at the client device, a request to obtain data stored at a server computer;

determining, by the client device, that caching is enabled at the client device based upon at least one of;

a user-selectable cache mode being enabled, or

the client device having a cache mode;

requesting, by the client device, the data stored at the server computer;

in response to the request for the data stored at the server, receiving hashes corresponding to the data instead of the requested data;

searching the cache for the hashes by;

determining that the hashes are received from the server computer, each of the requested hashes comprising unique data corresponding to the requested data; and

accessing the cache; and

in response to a determination that the cache does not include the hashes;

determining whether one or more local peers in communication with the client device has the data corresponding to the hashes;

determining which local peers have which portions of the data corresponding to the hashes; and

requesting respective portions of the data from the identified local peers.

2. The method of claim 1, wherein searching the cache for the hashes comprises:

receiving the hashes from the server computer; and

in response to determining that the cache does not store the hashes,

generating a request for the data and for the hashes, and

storing the data and the hashes in the cache.

3. The method of claim 1, wherein searching the cache for the hashes comprises:

in response to identifying the hashes in the cache, obtaining the data from the cache.

4. The method of claim 3, wherein the cache comprises a distributed cache provided by the client device and a client peer, and wherein obtaining the data from the cache comprises obtaining the data from the client peer.

5. The method of claim 4, wherein the client device and the client peer are located on a network with constrained bandwidth.

6. The method of claim 1, further comprising

generating new data at the client device;

uploading the new data to the server computer with a request for a hash corresponding to the new data;

receiving the hash from the server computer; and

storing the hash and the new data in the cache.

7. A client computer system:

a network interface unit in the client computer system;

a memory device in the client computer system, the memory device containing computer readable instructions; and

a processor in the client computer system, the processor communicatively coupled to the memory device and to the network interface unit, the processor executing the computer readable instructions to;

receive via the network interface unit a request to obtain data stored at a server computer;

determine whether caching is enabled at the client computer system and the server computer;

in response to determining that caching is not enabled at the client computer system and the server computer based upon a refusal to use a hash by the client computer system and the server computer, request, via the network interface unit, the data from the server computer;

in response to determining that caching is enabled at the client computer system based upon at least one of a user-selectable cache mode being enabled or the client computer system having a cache mode, and at the server computer based upon the server computer having the cache mode;

request, via the network interface unit, hashes from the server computer, the hashes corresponding to the data;

search a cache for the hashes by;

determining that the hashes are received from the server computer, each of the requested hashes comprising unique data corresponding to the requested data; and

accessing the cache;

in response to a determination that the cache does not include the hashes;

determine whether one or more local peers in communication with the client device has the data corresponding to the hashes;

determine which local peers have which portions of the data corresponding to the hashes; and

request respective portions of the data from the identified local peers.

8. The client computer system of claim 7, wherein the memory device further comprises computer readable instructions that, when executed by the processor, cause the processor to:

determine whether the cache stores the data;

in response to determining that the cache does not store the hash;

generate a request for the data from the server computer, and

store the data and the hash in the cache.

9. The client computer system of claim 8, wherein the memory device further comprises computer readable instructions that, when executed by the processor, cause the processor, in response to identifying the hash in the cache, to:

obtain the data from the cache.

10. The client computer system of claim 9, wherein the cache comprises a distributed cache provided by the client computer system and a client peer, and wherein obtaining the data from the cache comprises obtaining the data from the client peer.

11. The client computer system of claim 10, wherein the client computer system and the client peer are located at a branch office, and wherein the server computer is located remote from the branch office.

12. The client computer system of claim 7, wherein the memory device further comprises computer readable instructions that, when executed by the processor, cause the processor to:

generate new data at the client computer system;

upload, via the network interface unit, the new data to the server computer with a request for a new hash corresponding to the new data;

receive, via the network interface unit, the new hash from the server computer; and

store the new hash and the new data in the cache.

13. A computer-implemented method for managing a cache of data, the computer-implemented method comprising performing computer-implemented operations at a server for:

receiving a request for a hash from a client device;

determining that caching is enabled at the client device based on a user-selectable cache mode being enabled;

determining whether to send the hash or data corresponding to the hash based upon at least one of;

a size of the data compared to a size of the hash, a time required to generate the hash if the hash is not already stored at the server, or a number of communications required between the client device and the server if the data is not stored in the cache, wherein determining whether to send the hash or the data based on the number of required communications comprises determining the number of communications required between the client and the server if the data is not stored in the cache;

if it is determined to send the hash then sending the hash to the client device, wherein;

if the determination whether to send the hash or data is based on the number of communications required between the client device and the server, then sending the hash if fewer communications to send the hash are required relative to the number of communications required to send the data; and

if it is determined to send the data, then sending the data to the client device.

14. The computer-implemented method of claim 13, wherein the request for the hash from the client device comprises a request for data and a flag indicating that a hash should be sent, and the computer-implemented operations further comprise:

if the flag is present, then proceeding to the determining operation; and

if the flag is not present, then sending the data to the client device.

15. The computer-implemented method of claim 13 wherein the determining operation comprises:

comparing the size of the hash with the size of the data;

sending the data if that is more efficient than sending the hash; and

sending the hash if that is more efficient than sending the data.

16. The computer-implemented method of claim 15 and further comprising sending the data if the size of the data is approximately the size of the hash.

17. The computer-implemented method of claim 15 and further comprising storing a flag to indicate that the hash is to be provided in response to a future request from the client device.

18. The computer-implemented method of claim 13 wherein the determining operation comprises:

determining the time required to generate the hash if the hash is not already stored at the server;

generating the hash and sending the hash if that is more time-efficient than sending the data; and

sending the data if that is more time-efficient than generating and sending the hash.