 21 | to give 256KB disk accesses and use PersistenceManager L1 ref=soft caching and datastore pagefile caching 1 MB (4 256KB sized pages). The goal is to have frequent PersistenceManager L1 cache hit, then less frequent datastore pagefile cache hit, then when absolutely necessary, read/write from |
21 | (PersistenceManagerFactory scope) object data cache. Query program cache for repeating queries with different arguments. Query result cache for repeating queries with identical arguments. Improved configurable database page cache. Designed to support very large database files (terabytes). Reducing round |
21 | references to such cached result objects ? or do ObjectDB exploits frequency of querying such objects ... size of ObjectDB L2 cache or EntityManager context ? Q4: Would paging result sets ... (the EntityManager L1 cache) but instantiation of the results (if they contain entity objects |
21 | Are there some possibilities to configure following caches in order to keep cache data for only some important entity types and for the entire life cycle of the EntityManagerFactory. Cache of database file pages. Cache of query programs. Cache of query execution results. These caches are fully |
21 | Hello! I would like to use selective cache for JPA Level 2 (cached in EntityManagerFactory) in one app, but no cache at all in another app. Both will be connected to the same ObjectDB server & db ... #The_cache_element_ specifies only amount of MB used for Level 2 cache, but the config is at server |
21 | objectdb.conf has options for query results and program cache. (objectdb.conf > database > query-cache > results and programs, http://www.objectdb.com/java/jpa/setting/database#The_query-cache ... cache still available? Yes, these are server/store side caches. The exact client side code doesn't affect. BoydEdmondson |
21 | was load and the entity MyEntity1 is taken in the second level cache, the other entity types not ... list; } The 2nd level cache stores object data (byte[]) rather than live entity objects ... cache as object IDs (PK) encoded in the byte[] of a MyEntity1 instance. When you retrieve a MyEntity1 |
20 | attempting to keep the L1 cache within the PersistenceManager cleared in an effort to reduce its memory ... the cache?
try {
// Start the transaction
m_persistenceManager ... );
// Flush the JDO cache
m_persistenceManager.evictAll();
m |
20 | of interest to the listener Since: JDO 2.0 void checkConsistency() Validates the PersistenceManager cache with the datastore. Validates the PersistenceManager cache with the datastore. This method has no effect ... the consistency of instances in the cache against the datastore. An implementation might flush instances as |
20 | implementations allow instances to be cached in a second-level cache, and allow direct management of the cache by knowledgeable applications. This interface standardizes this behavior. Since: JDO 2.0 void evict(Object oid) Evict the parameter instance from the second-level cache. Evict the parameter |
