System and method for supporting a tiered cache

• US 8,700,855 B2
• Filed: 11/26/2012
• Issued: 04/15/2014
• Est. Priority Date: 01/31/2008
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Revanuru, Naresh
• Primary Examiner(s): Verbrugge, Kevin
• Application Number:
  US13/685,357
• Publication Number:
  US 20130086326A1
• Time in Patent Office: 505 Days
• Field of Search: None
• US Class Current: 711/122
• CPC Class Codes: G06F 12/0811 with multilevel cache hierarchies
• CPC Class Codes: G06F 12/0842 for multiprocessing or multitasking
• CPC Class Codes: G06F 12/0848 Partitioned cache, e.g. separate instruction and operand caches

Abstract

A computer-implemented method and system can support a tiered cache, which includes a first cache and a second cache. The first cache operates to receive a request to at least one of update and query the tiered cache; and the second cache operates to perform at least one of an updating operation and a querying operation with respect to the request via at least one of a forward strategy and a listening scheme.

Claims

1. A system to support a tiered cache running on one or more microprocessors, comprising:

a first cache that operates to receive a request to at least one of update and query the tiered cache; and

a second cache that operates to perform at least one of an updating operation and a querying operation with respect to the request via at least one of a forward strategy and a listening scheme, and

wherein the first cache and the second cache are capable of self-loading, and wherein the first cache and the second cache are synchronized using a paging coherency strategy.

2. The system according to claim 1, wherein:

the first cache is smaller and faster than the second cache.

3. The system according to claim 1, wherein:

the forward strategy includes at least one of;

vetoing any attempt to update;

applying immediately each update of the first cache to the second cache;

applying update of the first cache to the second cache only when the first cache evicts an entry; and

applying asynchronously each update of the first cache to the second cache.

4. The system according to claim 1, wherein:

the listening scheme includes at least one of;

no listening;

listening to all; and

listening selectively.

5. The system according to claim 1, wherein:

the tiered cache operates to hold a lock on one or more cache entries.

6. The system according to claim 1, wherein:

the tiered cache operates to group a set of cached objects to enable event processing, wherein cache actions can be automatically performed on related objects in the set of cached objects.

7. The system according to claim 1, wherein:

the tiered cache operates to update cache objects only at the end of a session.

8. The system according to claim 1, wherein:

the tiered cache operates to create the first cache and the second cache from a cache manager.

9. The system of claim 1, wherein:

the tiered cache operates to use a paging construct that is based on a tiered map.

10. The system of claim 1, wherein:

the paging coherency strategy allows that an update from the first cache to the second cache is applied only when the first cache evicts an entry.

11. The system of claim 1, wherein:

the first cache and the second cache reside on different virtual machine instances.

12. A computer-implemented method to support a tiered cache, comprising:

allowing a first cache to receive a request to at least one of update and query the tiered cache;

allowing a second cache to perform at least one of an updating operation and a querying operation with respect to the request via at least one of a forward strategy and a listening scheme; and

allowing the first cache and the second cache to be capable of self-loading, and wherein the first cache and the second cache are synchronized using a paging coherency strategy.

13. The method according to claim 12, further comprising:

allowing the first cache to be smaller and faster than the second cache.

14. The method according to claim 12, further comprising:

allowing the forward strategy to include at least one of;

vetoing any attempt to update;

applying immediately each update of the first cache to the second cache;

applying update of the first cache to the second cache only when the first cache evicts an entry; and

applying asynchronously each update of the first cache to the second cache.

15. The method according to claim 12, further comprising:

allowing the listening scheme includes at least one of;

no listening;

listening to all; and

listening selectively.

16. The method according to claim 12, further comprising:

holding a lock on one or more cache entries.

17. The method according to claim 12, further comprising:

grouping a set of cached objects to enable event processing, wherein cache actions are automatically performed on related objects in the set of cached objects.

18. The method according to claim 12, further comprising:

updating cache objects only at the end of a session.

19. The method according to claim 12, further comprising:

creating the first cache and the second cache from a cache manager.

20. A machine readable medium having instructions stored thereon that when executed cause a system to perform the steps comprising:

allowing a first cache to receive a request to at least one of update and query the tiered cache;

allowing a second cache to perform at least one of an updating operation and a querying operation with respect to the request via at least one of a forward strategy and a listening scheme; and

allowing the first cache and the second cache to be capable of self-loading, and wherein the first cache and the second cache are synchronized using a paging coherency strategy.