Systems and methods for dynamic control of cache and pool sizes using a batch scheduler

• US 7,543,273 B2
• Filed: 10/15/2004
• Issued: 06/02/2009
• Est. Priority Date: 05/21/2004
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Chow, Thorick, White, Seth
• Primary Examiner(s): KIM, HONG CHONG
• Application Number:
  US10/966,766
• Publication Number:
  US 20050262516A1
• Time in Patent Office: 1,691 Days
• Field of Search: 711/118, 711/133, 711/134, 711/159, 711/170, 707/103.R, 707/205, 718/102, 719/315, 719/332, 709/217, 717/116, 717/118
• US Class Current: 717/118
• CPC Class Codes: G06F 12/023 Free address space management
• CPC Class Codes: G06F 12/0891 using clearing, invalidating or resetting means
• CPC Class Codes: G06F 9/5016 the resource being the memory

Abstract

The present invention provides users and processes with various features to control the memory usage by a cache and pool dynamically at runtime. The cache and pool can be initialized on demand to remove idle objects of classes from them without the server being restarted. When the cache and pool reach their maximum sizes, idle objects in them may be removed to make room for newly active objects using various strategies in batches, where the schedule (periodicity), size and processing time of each batch can be dynamically adjusted. When a newly created object is being added to a full cache where each object is enrolled in a transaction, one or more active objects may be passivated from the cache based on various criteria to make room for the new instance to be added. Various features of the cache and pool can be defined in a configuration file. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Claims

1. A system to support dynamic control of cache, comprising:

a cache to store in memory one or more objects of each of one or more classes defined by an object-oriented programming language;

one or more properties associated with a class of the one or more classes;

a configuration file to define the one or more properties associated with the class; and

a cache control component configured to perform steps of;

instantiating and/or adding the object into the cache;

removing the object, even if the object is an active object, from the cache when the cache is full and another object is to be inserted, wherein the active object is involved in a transaction and is accessible via the cache during a whole transaction period; and

deploying a batch scheduler to perform the removing step via one or more batches;

wherein the batch scheduler is a self-correcting batch scheduler with time-slice feedback mechanism to set a size of a batch of the one or more batches, wherein the batch scheduler is configured to perform at least one of;

executing the batch at a fixed or variable periodicity;

locking the cache when executing the batch;

setting a processing time for the batch;

setting the size of the batch, i.e., the number of instances to be processed by the batch;

calculating the processing time for each instance by the batch; and

adjusting the processing time for the batch and/or the size of the batch based on the processing time for each instance.

2. The system according to claim 1, wherein:

the object-oriented programming language can be Java®

or C++.

3. The system according to claim 1, wherein:

the class can be one of an interface, a module, a Java®

bean and an Enterprise Java®

Bean type.

4. The system according to claim 1, wherein:

a property in the one or more properties can be a limit on the idle time allowed for an object of the class.

5. The system according to claim 1, wherein:

the cache control component is capable of removing the object from the cache if the idle time of the object is greater than the limit on the idle time allowed for the class of the object.

6. The system according to claim 1, wherein:

the cache control component is capable of removing the instance that has the longest idle time first.

7. The system according to claim 1, further comprising:

a pool capable of storing in memory one or more objects of each of one or more classes; and

a pool control component capable of performing on an object in the one or more objects;

preloading the object into the pool at deployment time up to a pre-defined initial pool size limit and setting the idle time of the object to zero;

monitoring the idle time of the object; and

removing the object from the pool if one or more criteria are met.

8. The system according to claim 7, wherein:

a property in the one or more properties can be at least one of;

a limit on the idle time allowed for an object of the class; and

the initial size of the pool for the class, i.e., the initial number of objects of the class allowed in the pool.

9. The system according to claim 7, wherein:

a criterion in the one or more criteria can be at least one of;

the idle time of the object is greater than the limit on the idle time allowed for the class of the object; and

the size of the pool for the class is greater than the initial size of the pool for the class.

10. The system according to claim 1, wherein:

the cache control component is capable of setting the idle time of the object to zero and monitoring the active and/or idle time of the object.

11. A system to support dynamic control of cache, comprising:

a cache to store in memory one or more instances of each of one or more Enterprise Java®

Bean (EJB) types;

one or more properties associated with an EJB type of the one or more EJB types;

a deployment descriptor to define the one or more properties associated with the EJB type; and

a cache control component configured to perform steps of;

instantiating and/or adding the instance into the cache;

removing the instance, even if the object is an active instance, from the cache when the cache is full and another instance is to be inserted, wherein the active instance is involved in a transaction and is accessible via the cache during a whole transaction period; and

deploying a batch scheduler to perform the removing step via one or more batches;

wherein the batch scheduler is a self-correcting batch scheduler with time-slice feedback mechanism to set a size of a batch of the one or more batches, wherein the batch scheduler is configured to perform at least one of;

executing the batch at a fixed or variable periodicity;

locking the cache when executing the batch;

setting a processing time for the batch;

setting the size of the batch, i.e., the number of instances to be processed by the batch;

calculating the processing time for each instance by the batch; and

adjusting the processing time for the batch and/or the size of the batch based on the processing time for each instance.

12. The system according to claim 11, wherein:

the deployment descriptor is capable of defining the one or more properties in a markup language.

13. The system according to claim 11, wherein:

the cache control component is capable of setting the idle time of the instance to zero and monitoring the active and/or idle time of the instance.

14. The system according to claim 11, further comprising:

a pool capable of storing in memory one or more instances of each of one or more EJB types; and

a pool control component capable of performing on an instance in the one or more instances;

preloading the instance into the pool at deployment up to a pre-defined initial pool size limit and setting the idle time of the instance to zero;

monitoring the idle time of the instance; and

removing the instance from the pool if one or more criteria are met.

15. The system according to claim 14, wherein:

the deployment descriptor is capable of defining the one or more properties in a markup language.

16. A method to support dynamic control of cache, comprising:

storing in memory one or more objects of each of one or more classes defined by an object-oriented programming language via a cache;

defining one or more properties associated with a class of the one or more classes via a configuration file; and

performing on an object in the one or more objects;

instantiating and/or adding the object into the cache;

removing the object, even if the object is an active object, from the cache when the cache is full and another object is to be inserted, wherein the active object is involved in a transaction and is accessible via the cache during a whole transaction period; and

deploying a batch scheduler to perform the removing step via one or more batches;

wherein the batch scheduler is a self-correcting batch scheduler with time-slice feedback mechanism to set a size of a batch of the one or more batches, wherein the batch scheduler is configured to perform at least one of;

executing the batch at a fixed or variable periodicity;

locking the cache when executing the batch;

setting a processing time for the batch;

setting the size of the batch, i.e., the number of instances to be processed by the batch;

calculating the processing time for each instance by the batch; and

adjusting the processing time for the batch and/or the size of the batch based on the processing time for each instance.

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

removing the instance that has the longest idle time first.

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

storing in memory one or more objects of each of one or more classes via a pool; and

performing on an object in the one or more objects;

preloading the object into the pool at deployment up to a pre-defined initial pool size limit and setting the idle time of the object to zero;

monitoring the idle time of the object; and

removing the object from the pool if one or more criteria are met.

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

performing on an object in the one or more objects setting the idle time of the object to zero and monitoring the active and/or idle time of the object.

20. A method to support dynamic control of cache, comprising:

storing in memory one or more instances of each of one or more Enterprise Java®

Bean (EJB) types via a cache;

defining one or more properties associated with an EJB type of the one or more EJB types via a deployment descriptor; and

performing on an instance in the one or more instances;

instantiating and/or adding the instance into the cache;

removing the instance, even if the object is an active instance, from the cache when the cache is full and another instance is to be inserted, wherein the active instance is involved in a transaction and is accessible via the cache during a whole transaction period; and

deploying a batch scheduler to perform the removing step via one or more batches;

wherein the batch scheduler is a self-correcting batch scheduler with time-slice feedback mechanism to set a size of a batch of the one or more batches, wherein the batch scheduler is configured to perform at least one of;

executing the batch at a fixed or variable periodicity;

locking the cache when executing the batch;

setting a processing time for the batch;

setting the size of the batch, i.e., the number of instances to be processed by the batch;

calculating the processing time for each instance by the batch; and

adjusting the processing time for the batch and/or the size of the batch based on the processing time for each instance.

21. The method according to claim 20, further comprising:

defining the one or more properties in a markup language.

22. The method according to claim 20, further comprising:

performing on an instance in the one or more instances setting the idle time of the instance to zero and monitoring the active and/or idle time of the instance.

23. The method according to claim 20, further comprising:

storing in memory one or more instances of each of one or more EJB types via a pool; and

performing on an instance in the one or more instances;

preloading the instance into the pool at deployment time up to a pre-defined initial pool size limit and setting the idle time of the instance to zero;

monitoring the idle time of the instance; and

removing the instance from the pool if one or more criteria are met.

24. The method according to claim 23, further comprising:

defining the one or more properties in a markup language.

25. A machine readable medium having instructions stored thereon that when executed cause a system to:

store in memory one or more objects of each of one or more classes defined by an object-oriented programming language via a cache; and

perform on an object in the one or more objects;

instantiating and/or adding the object into the cache;

removing the object, even if the object is an active object, from the cache when the cache is full and another object is to be inserted, wherein the active object is involved in a transaction and is accessible via the cache during a whole transaction period; and

deploying a batch scheduler to perform the removing step via one or more batches;

wherein the batch scheduler is a self-correcting batch scheduler with time-slice feedback mechanism to set a size of a batch of the one or more batches, wherein the batch scheduler is configured to perform at least one of;

executing the batch at a fixed or variable periodicity;

locking the cache when executing the batch;

setting a processing time for the batch;

setting the size of the batch, i.e., the number of instances to be processed by the batch;

calculating the processing time for each instance by the batch; and

adjusting the processing time for the batch and/or the size of the batch based on the processing time for each instance.

26. The machine readable medium of claim 25, further comprising instructions that when executed cause the system to:

remove the instance that has the longest idle time first.

27. The machine readable medium of claim 25, wherein:

store in memory one or more objects of each of one or more classes via a pool; and

perform on an object in the one or more objects;

preloading the object into the pool at deployment time up to a pre-defined initial

pool size limit and setting the idle time of the object to zero;

monitoring the idle time of the object; and

removing the object from the pool if one or more criteria are met.

28. The machine readable medium of claim 25, further comprising instructions that when executed cause the system to:

perform on an object in the one or more objects setting the idle time of the object to zero and monitoring the active and/or idle time of the object.

29. A machine readable medium having instructions stored thereon that when executed cause a system to:

store in memory one or more instances of each of one or more Enterprise Java®

Bean (EJB) types via a cache;

define one or more properties associated with an EJB type of the one or more EJB types via a deployment descriptor; and

perform on an instance in the one or more instances;

instantiating and/or adding the instance into the cache;

removing the instance, even if the object is an active instance, from the cache when the cache is full and another instance is to be inserted, wherein the active instance is involved in a transaction and is accessible via the cache during a whole transaction period; and

deploying a batch scheduler to perform the removing step via one or more batches;

wherein the batch scheduler is a self-correcting batch scheduler with time-slice feedback mechanism to set a size of a batch of the one or more batches, wherein the batch scheduler is configured to perform at least one of;

executing the batch at a fixed or variable periodicity;

locking the cache when executing the batch;

setting a processing time for the batch;

setting the size of the batch, i.e., the number of instances to be processed by the batch;

calculating the processing time for each instance by the batch; and

adjusting the processing time for the batch and/or the size of the batch based on the processing time for each instance.

30. The machine readable medium of claim 29, further comprising instructions that when executed cause the system to:

define the one or more properties in a markup language.

31. The machine readable medium of claim 29, further comprising instructions that when executed cause the system to:

perform on an instance in the one or more instances setting the idle time of the instance to zero and monitoring the active and/or idle time of the instance.

32. The machine readable medium of claim 29, wherein:

store in memory one or more instances of each of one or more EJB types via a pool; and

perform on an instance in the one or more instances;

preloading the instance into the pool at deployment time up to a pre-defined initial pool size limit and setting the idle time of the instance to zero;

monitoring the idle time of the instance; and

removing the instance from the pool if one or more criteria are met.

33. The machine readable medium of claim 32, further comprising instructions that when executed cause the system to:

define the one or more properties in a markup language.

34. A system to support dynamic control of cache, comprising:

means for storing in memory one or more objects of each of one or more classes defined by an object-oriented programming language via a cache;

means for defining one or more properties associated with a class of the one or more classes via a configuration file; and

means for performing on an object in the one or more objects;

instantiating and/or adding the object into the cache;

removing the object, even if the object is an active object, from the cache when the cache is full and another object is to be inserted, wherein the active object is involved in a transaction and is accessible via the cache during a whole transaction period; and

deploying a batch scheduler to perform the removing step via one or more batches;

wherein the batch scheduler is a self-correcting batch scheduler with time-slice feedback mechanism to set a size of a batch of the one or more batches, wherein the batch scheduler is configured to perform at least one of;

executing the batch at a fixed or variable periodicity;

locking the cache when executing the batch;

setting a processing time for the batch;

setting the size of the batch, i.e., the number of instances to be processed by the batch;

calculating the processing time for each instance by the batch; and

adjusting the processing time for the batch and/or the size of the batch based on the processing time for each instance.

35. The system according to claim 34, further comprising:

means for performing on an object in the one or more objects setting the idle time of the object to zero and monitoring the active and/or idle time of the object.

36. The system according to claim 34, further comprising:

means for storing in memory one or more objects of each of one or more classes via a pool; and

means for performing on an object in the one or more objects;

preloading the object into the pool at deployment up to a pre-defined initial pool size limit and setting the idle time of the object to zero;

monitoring the idle time of the object; and

removing the object from the pool if one or more criteria are met.

37. A system to support dynamic control of cache, comprising:

means for storing in memory one or more instances of each of one or more Enterprise Java®

Bean (EJB) types via a cache;

means for defining one or more properties associated with an EJB type of the one or more EJB types via a deployment descriptor; and

means for performing on an instance in the one or more instances;

instantiating and/or adding the instance into the cache;

removing the instance, even if the object is an active instance, from the cache when the cache is full and another instance is to be inserted, wherein the active instance is involved in a transaction and is accessible via the cache during a whole transaction period; and

deploying a batch scheduler to perform the removing step via one or more batches;

wherein the batch scheduler is a self-correcting batch scheduler with time-slice feedback mechanism to set a size of a batch of the one or more batches, wherein the batch scheduler is configured to perform at least one of;

executing the batch at a fixed or variable periodicity;

locking the cache when executing the batch;

setting a processing time for the batch;

setting the size of the batch, i.e., the number of instances to be processed by the batch;

calculating the processing time for each instance by the batch; and

adjusting the processing time for the batch and/or the size of the batch based on the processing time for each instance.

38. The system according to claim 37, further comprising:

means for storing in memory one or more instances of each of one or more EJB types via a pool; and

means for performing on an instance in the one or more instances;

preloading the instance into the pool at deployment time up to a pre-defined initial pool size limit and setting the idle time of the instance to zero;

monitoring the idle time of the instance; and

removing the instance from the pool if one or more criteria are met.

39. The system according to claim 37, further comprising:

means for performing on an instance in the one or more instances setting the idle time of the instance to zero and monitoring the active and/or idle time of the instance.