How can I tune JEs cache management policy for my applications access pattern?
JE, like most databases, performs best when database objects are found in its cache. The cache eviction algorithm is the way in which JE decides to remove objects from the cache and can be a useful policy to tune. The default cache eviction policy is LRU (least recently used) based. Database objects that are accessed most recently are kept within cache, while older database objects are evicted when the cache is full. LRU suits applications where the working set can stay in cache and/or there are some data records are used more frequently than others. An alternative cache eviction policy was added in JE 2.0.83 that is instead primarily based on the level of the node in the Btree.
