Dynamic object usage pattern learning and efficient caching

• US 20030105857A1
• Filed: 11/30/2001
• Published: 06/05/2003
• Est. Priority Date: 11/30/2001
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Ali, Syed M., Kamen, Yury, Daniels, Bruce K., Yared, Peter A., Goldberg, Robert N.
• Granted Patent: US 7,062,756 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• 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/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/5681 Pre-fetching or pre-delivering data based on network characteristics
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method for transparently optimizing data access. The method includes gathering information related to data usage when a system is processing and determining a usage pattern of the system using gathered information.

Claims

1. A method for transparently optimizing data access, comprising:

gathering information related to data usage when a system is processing; and

determining a usage pattern of the system using gathered information.

2. The method of claim 1, further comprising:

pre-fetching data determined by the usage pattern of the system;

caching data locally;

accessing data by the system; and

synchronizing cached data with persistent data.

3. The method of claim 1, further comprising:

generating a description of a business process model by retaining the usage pattern over a period of at least one execution of the system.

4. The method of claim 1, further comprising:

generating tests for the system by retaining the usage pattern over a period of at least one execution of the system.

5. The method of claim 1, wherein the usage pattern comprises pieces of information used together based on a relationship.

6. The method of claim 5, wherein the relationship is temporal.

7. The method of claim 5, wherein the relationship is causal.

8. The method of claim 1, further comprising:

deriving an initial usage pattern from application code analysis.

9. The method of claim 1, further comprising:

deriving an initial usage pattern from an empty set.

10. The method of claim 1, further comprising:

deriving an initial usage pattern from a specification.

11. The method of claim 1, further comprising:

displaying the usage pattern to a display device.

12. The method of claim 1, further comprising:

generating documentation from the usage pattern.

13. A method for transparently optimizing data access, comprising:

gathering information related to data usage when a system is processing;

determining a usage pattern of the system using gathered information;

pre-fetching data determined by the usage pattern of the system;

caching data locally;

accessing data by the system; and

synchronizing cached data with persistent data.

14. A method for transparently optimizing a distributed application having a client-side and a server-side, comprising:

gathering information related to data usage on the client-side when the distributed application is processing; and

determining a usage pattern using gathered information.

15. The method of claim 14, further comprising:

pre-fetching data from the server-side;

caching data on the client-side;

accessing data on the client-side; and

synchronizing cached data on the client-side with persistent data on the server-side.

16. The method of claim 14, wherein the usage pattern comprises pieces of information used together based on a relationship.

17. The method of claim 16, wherein the relationship is temporal.

18. The method of claim 16, wherein the relationship is causal.

19. The method of claim 14, wherein the data represents objects.

20. The method of claim 14, further comprising:

deriving an initial usage pattern from application code analysis.

21. The method of claim 14, further comprising:

deriving an initial usage pattern from an empty set.

22. The method of claim 14, further comprising:

deriving an initial usage pattern from a specification.

23. The method of claim 14, further comprising:

displaying the usage pattern to a display device.

24. The method of claim 14, further comprising:

generating documentation from the usage pattern.

25. A method for transparently optimizing a distributed application having a client-side and a server-side, comprising:

gathering information related to data usage on the client-side when the distributed application is processing;

determining a usage pattern using gathered information;

pre-fetching data from the server-side;

caching data on the client-side;

accessing data on the client-side; and

synchronizing cached data on the client-side with persistent data on the server-side.

26. A computer-readable medium having recorded thereon instructions executable by processing, the instructions for:

gathering information related to data usage when a system is processing;

determining a usage pattern of the system using gathered information;

pre-fetching data determined by the usage pattern of the system;

caching data locally;

accessing data by the system; and

synchronizing cached data with persistent data.

27. An apparatus for transparently optimizing data access, comprising:

means for gathering information related to data usage when a system is processing;

means for determining a usage pattern of the system using gathered information;

means for pre-fetching data determined by the usage pattern of the system;

means for caching data locally;

means for accessing data by the system; and

means for synchronizing cached data with persistent data.