Abstract: A method is described by defining one or more classes within a software application as being in scope, any class not defined as being in scope are defined as being out of scope, all classes comprise at least one method. The method further determines an amount of allocated memory for each of said in scope classes and said out of scope classes. Lastly, if one of said methods from one of said out of scope classes are called as a result of the calling of one of the in scope classes, adding said allocated memory from said out of scope class to said allocated memory of said in scope class.

Abstract: A database garbage collector that removes appropriate database entries accessed during a recent transaction.

Abstract: A method is described that involves hashing a key value to locate a slot in a primary table, then, hashing the key value to locate a first slot in a secondary table, then, linearly probing the secondary table starting from the first slot.

Abstract: Embodiments of the invention are generally directed to a system and method for object persistence. In an embodiment, a proxy object is created based, at least in part, on object metadata stored in an internal data store of a persistence manager. The persistence manager may receive a request to access member data of a persistent object associated with the proxy object. In one embodiment, the persistence manager provides the member data from the proxy object.

Abstract: A database garbage collector that removes appropriate database entries accessed during a recent transaction.