Universal cache management system

Patent metadata

Field	Value
Publication number	US-9703706-B2
Application number	US-201113037172-A
Country	US
Kind code	B2
Filing date	Feb 28, 2011
Priority date	Feb 28, 2011
Publication date	Jul 11, 2017
Grant date	Jul 11, 2017

Abstract

Techniques for universal cache management are described. In an example embodiment, a plurality of caches are allocated, in volatile memory of a computing device, to a plurality of data-processing instances, where each one of the plurality of caches is exclusively allocated to a separate one of the plurality of data-processing instances. A common cache is allocated in the volatile memory of the computing device, where the common cache is shared by the plurality of data-processing instances. Each instance of the plurality of data-processing instances is configured to: identify a data block in the particular cache allocated to that instance, where the data block has not been changed since the data block was last persistently written to one or more storage devices; cause the data block to be stored in the common cache; and remove the data block from the particular cache. Data blocks in the common cache are maintained without being persistently written to the one or more storage devices.

First claim

What is claimed is:

1. A method comprising:
allocating, in volatile memory of a Symmetric Multi Processor (SMP) machine, a first cache exclusively to a first instance of two or more data-processing instances, wherein the first cache is configured to store copies of a first set of data blocks that are persistently stored on one or more storage devices, and wherein the allocating the first cache is performed, at least in part, by an operating system (OS) instance;
allocating, in the same volatile memory of the SMP machine, a second cache exclusively to a second instance of the two or more data-processing instances, wherein the second cache is configured to store copies of a second set of data blocks that are persistently stored on the one or more storage devices, and wherein the allocating the second cache is performed, at least in part, by the OS instance;
allocating at least a portion of a common cache in the same volatile memory of the SMP machine, wherein the allocating at least a portion of the common cache is performed, at least in part, by the OS instance;
the first instance performing the steps of:
identifying for eviction from the first cache a first data block at least because the first data block has not been changed since the first data block was last persistently written to the one or more storage devices;
in response to identifying for eviction from the first cache a first data block at least because the first data block has not been changed since the first data block was last persistently written to the one or more storage devices:
causing the first data block to be stored in the common cache, and
removing the first data block from the first cache;

the second instance performing the steps of:
identifying for eviction from the second cache a second data block at least because the second data block has not been changed since the second data block was last persistently written to the one or more storage devices:
in response to identifying for eviction from the second cache a second data block at least because the second data block has not been changed since the second data block was last persistently written to the one or more storage devices:
causing the second data block to be stored in the common cache, and
removing the second data block from the second cache;

maintaining data blocks, including the first data block and the second data block, in the common cache without persistently writing the data blocks to the one or more storage devices; and
wherein the method is performed by the SMP machine.

2. The method of claim 1 , wherein the two or more data-processing instances are two or more database instances that manage one or more databases that are stored on the one or more storage devices.

3. The method of claim 1 , wherein allocating at least a portion of the common cache comprises one or more of:
allocating the common cache in physical memory of the SMP machine; and
allocating a first portion of the common cache on the physical memory of the SMP machine and a second portion of the common cache on a flash memory that is attached to the SMP machine.

4. The method of claim 1 , wherein maintaining the data blocks in the common cache comprises maintaining block-identifying data for each of the data blocks stored in the common cache.

5. The method of claim 1 , wherein maintaining the data blocks in the common cache comprises:
maintaining the first data block in the common cache across a restart of the first instance; and
maintaining the second data block in the common cache across a restart of the second instance.

6. The method of claim 1 , further comprising:
in response to a first request for data from the first data block, the first instance retrieving the first data block from the common cache instead of the one or more storage devices, and storing the first data block back into the first cache;
in response to a second request for data from the second data block, the second instance retrieving the second data block from the common cache instead of the one or more storage devices, and storing the second data block back into the second cache.

7. The method of claim 1 , further comprising:
in response to a request for data from the second data block, the first instance retrieving the second data block from the common cache instead of the one or more storage devices, and storing the second data block into the first cache.

8. The method of claim 1 , further comprising:
the first instance sending a request for a third data block to an instance that manages the common cache;
the instance that manages the common cache performing the steps of:
determining that the third data block is not stored in the common cache;
retrieving the third data block from a different common cache that is allocated on a different SMP machine; and
returning the third data block to the first instance.

9. The method of claim 1 , further comprising:
the first instance requesting the first data block from the common cache;
determining that the first data block is not stored in the common cache; and
retrieving the first data block from the one or more storage devices, wherein retrieving the first data block comprises one of:
the first instance retrieving the first data block from the one or more storage devices; or
an instance that manages the common cache retrieving the first data block from the one or more storage devices and returning the first data block to the first instance.

10. The method of claim 1 , further comprising:
after the first instance restarts, the first instance warming up the first cache by retrieving at least the first data block from the common cache instead of the one or more storage devices and storing the first data block back into the first cache; and
after the second instance restarts, the second instance warming up the second cache by retrieving at least the second data block from the common cache instead of the one or more storage devices and storing the second data block back into the second cache.

11. The method of claim 1 , wherein the common cache comprises a third set of clean data blocks that are persistently stored on one or more storage devices, and wherein each particular clean data block of the third set of clean data blocks not been changed since the particular clean data block was last persistently written to the one or more storage devices.

12. The method of claim 1 , wherein allocating the first cache comprises:
allocating, by the OS instance, a first range of memory addresses to the first instance;
allocating, by the first instance, a subset of the first range of memory addresses to the first cache; and

wherein allocating the second cache comprises:
allocating, by the OS instance, a second range of memory addresses to the second instance;
allocating, by the second instance, a subset of the second range of memory addresses to the second cache.

13. The method of claim 1 , wherein allocating the first cache comprises allocating, by the OS instance, a first range of memory addresses to the first cache and wherein allocating the second cache comprises allocating, by the OS instance, a second range of memory addresses to the second cache.

14. A method comprising:
allocating, in volatile memory of a computing device, a plurality of caches to a plurality of database instances, wherein each one of the plurality of caches is exclusively allocated to a separate database instance of said plurality of database instances to change data blocks stored in said each one of said plurality of caches that are modified by a transaction, wherein the allocating the plurali

Assignees

• Bagal Prasad V
• Long Rich
• Oracle Int Corp

Inventors

• Bagal Prasad V
• Long Rich

Classifications

• G06F2212/1048

  Scalability · CPC title

• G06F12/0871

  Allocation or management of cache space · CPC title

• G06F12/0897

  with two or more cache hierarchy levels (with multilevel cache hierarchies G06F12/0811) · CPC title

• G06F12/084

  with a shared cache · CPC title

• G06F17/3048

  Physics · mapped topic