ObjectDB Database Search

.fetch(ResultSet.java:189) at org.eclipse.birt.data.engine.executor. cache .OdiAdapter.fetch(OdiAdapter.java:214) at org.eclipse.birt.data.engine.executor. cache .RowResultSet.fetch(RowResultSet.java:145) at org.eclipse.birt.data.engine.executor. cache .RowResultSet.doNext(RowResultSet.java:118) at org

cache configuration:    level2="0mb" - 20 msec query    level2="2mb" - 10 msec    level2="10mb" - 40 msec Question: why is a larger level2 cache worse than no level2 cache , ie 10mb worse than 0mb? 2) (separate issue) I'm noticing that write queries are around 20-50x

disk database, with a large memory cache . In addition,  the operating system usually uses free physical memory as cache , so you may find that you get the performance that you need ... is going to make inefficient use of my memory, however your alternative option of larger memory cache

first). Larger  processing = cache value. More RAM on the machine. Using a dedicated disk ... the load. The number of threads it was actually using was 380. How is larger processing = cache value ... a bad thing.  How is larger processing = cache value is going to reduce duration of a single

Hello , I need advanced caching system. Terracotta ehcache provides us , advanced distributed cache mechanism.   Can we use objectdb with ehcache ?   kadirbasol Kadir BASOL ObjectDB uses its own non pluggable cache , so currently it cannot be replaced with another cache

getting data from the L2 data cache (e.g., due to limited RAM and large cache that might be swapped to the disk?). Try to disable the L2 data cache or decrease its size, assuming you use it. support Support Our second level cache is not activated: Do you have another explanation? btc_es BTC

) at eu.ysoft.commons.logging.LogFactory.getLog(LogFactory.java:32) at eu.ysoft.safeq.core. cache .entity ... .safeq.core. cache .entity.CacheableDriverProperty at com.objectdb.o.JEW.aK(JEW.java:185)    ... dump was taken while the Enhancer was analyzing the class  eu.ysoft.safeq.core. cache .entity

the application cache only some embedded parts of those objects (let's call them class B). This application cache should work independently on the DB as if it contained transient objects. However those instances ... the application point-of-view. So as long as I keep B in application cache , also A is present in

is tight, you may have to reduce the sizes of the processing cache , the L2 data cache , and the query results cache . support Support

. Do you have another idea? btc_es BTC EmbeddedSystems In that case, maybe it is related to the query cache , although such an issue is not expected. You may try disabling the query cache to see if it helps ... with the deactivated query cache works. But the question is now why? The DB Doctor does not show errors

, the problem now is different. Could you please post your objectdb.conf file? The database cache ... which was enabled in default conf: madhuarish Bhanu Pathak The cache should be 64MB per open database, so assuming you have one open database there is a cache memory problem. The heap dump may help in

to perform some custom code when instantiating the object i can keep the cache and make sure that in any ... have this feature, (and L1 or L2 cache is not a guarantee that i'll get the same object ... to perform some custom code when instantiating the object i can keep the cache and make sure

. For example, the  EntityManager may not be aware that a cached entity object in its persistence ... more the SQL way than the JPA way. Clear the internal EntityManager cache by using clear after an UPDATE query and before retrieval or a specific object using refresh , and disable the 2nd level cache

Processing (server side) cache size Query cache size Client side cache settings You may try each

. we wonder if the cache and other settings can be optimized to get the most performance ... general:temp:threshold value can reduce temporary files usage. The L2 cache does not always help so you can try with and without (i.e. disabled). The query result cache is effective if your application

SSD could help. Increasing the page cache may help. By running replications of your database ... we already have a 2GByte page cache for a 30 GByte database file. Should we increase ? Database is on SSD ... ;     hgzwicker Hans-Georg Zwicker Increasing the cache may help, so you may want to try

Ken If you could retrieve old objects but not the recently stored objects then this could be a cache ... cache is enabled. support Support Your test demonstrates a bug in the ObjectDB query program cache

and the query program cache cannot be used. Maybe ObjectDB should optimize such queries replacing literals ... . So ObjectDB would indeed cache this query the way it is? Please ignore my original post - the literals ... ObjectDB on every call and cache will be used. Additional optimization can be achieved by: Reusing

You should be able to use ObjectDB successfully as an image database. ObjectDB includes many types of cache ... changing the default reference cache configuration from weak to soft or strong. However, notice that objects are cached as objects per EntityManager , so you will have to use long term shared EntityManager to benefit from this object pooling. support Support

in every object retrieval is setting the id. Maybe you retrieve a cached object from memory ... cache makes a difference, as well as disabling caches in the configuration. You may also try

, and maybe some cache issue.    support Support Interesting, especially because I ... ) PS. Now I'm writing from IE. zmirc Mircea Chirac To check if this is a cache issue ... by JavaScript / CSS on the client side (based on cookies). This enables better caching

from the cache and it should therefore not include it in its list of objects.  Maybe it only does that for its iterator() object and perhaps does not respect the cache when using the Extent in ... the cache , like it was told to do).  If I manually set ignoreCache=false to correct the failure

the filesystem. I would like to enable the level2 cache for all entities:  https://www.objectdb.com/java/jpa/setting/entities#The_ cache _element a) Is it possible to configure this 

don't have the cached Document and then find the Document by Id. - At that point the Document ... because I have the cached value of the Document returned.   @Entity public class Document { private

bug in transaction isolation or cache management. Anyway, a test case that reproduces the problem ... it has something to do with something being cached or not cleaned up after the creation.   I can't

are per database. For example, the default cache size for database pages is 64GB per database, or 6.4GB per 100 databases, so it can easily exceeds your VPS RAM. If you must keep 100 databases open concurrently then you will have to reduce cache sizes, etc. support Support

Configuration : ObjectDB Version: 2.8.8 VM Total Memory: 90GB ObjectDB Configuration: Processing Cache ... the server is started. I have already tried reducing the processing cache and monitoring system resource

) after restart and not reported by the Doctor are not corruption errors but related to cache , and will not cause data loss. These cache errors have been addressed by fixes in recent versions

discard cached objects in the EntityManager and in the L2 cache .  support Support

Support The screen shots may indicate a problem in the page cache (which keeps too many pages ... : The element - try reducing the number of threads and the cache size (notice that this setting

trans is not a transaction of em . Maybe different EntityManager instances are used and the L2 cache is enabled. support Support L2 cache ? I'm not sure. But why the second find() will output? By

classes. Reduce cache size. You can disable the L2 data cache by setting its size to 0. Use smaller

index: @Index(members={"startDate", "toExtension"}),   We tried clearing the EntityManager cache ... ? 3. Can you give us details on how you implement the L1 and L2 caches ?   Thank you Emil  

are loaded from disk to RAM (when needed). Therefore, unless the database file is small and cached completely (by ObjectDB or OS cache ), SSD is expected to be faster, since it significantly reduces

cache size Query results cache size support Support Upping the max heap size to 256M has solved this problem. Thank you! banglo mohammad haroon

data cache is enabled you have to use refresh or refreshAll in order to bypass that cache as

page size of presumably 256 KB.  (So I was wasting a lot of RAM and resources like caching based on 256 KB when I only needed 64 KB based size support caches , etc.)   Thanks

different threads, increasing the effectiveness of the EntityManager's persistence context (L1) cache . But otherwise read only databases are not faster. Future versions of ObjectDB might share an L1 cache

.PersistenceException Failed to read from file 'C:\SafeQORS\server\ cache \MainORSCache.odb' (error 117 ... ) at com.ysoft. cache .objectdb.ObjectCacheDB.deleteInOpenTransaction(ObjectCacheDB.java:361) at com.ysoft. cache .objectdb.ObjectCacheDB.delete(ObjectCacheDB.java:356) at com.ysoft. cache .objectdb

The two thread dumps show two different waiting situations. The first thread dump shows a page cache lock ... at the ObjectDB level. There is a query cache of course, but it is useful for getting query results quickly ... . The objects that are added to the heap are related to: (1) the L2 cache , (2) the query caches

if possible. felixobjectdb Richard Szurgot It was a bug in the page cache . This cache can hold ... when the operation has started). You cannot disable that cache since it has a minimum size even if you request zero ... ) - the page cache could purge newer version of a page leaving older versions for use by newer users

.core. cache .entity.CacheableJobInfo.__odbGet_id(CacheableJobInfo.java:1) at eu.ysoft.safeq.core. cache .entity.CacheableJobInfo.getPrimaryKey(CacheableJobInfo.java:828) at eu.ysoft. cache .cluster.bucket.Bucket.add(Bucket.java:36) at com.ysoft. cache .objectdb.cluster.bucket.ObjectCacheDBBucketManager

. Both have been updated yesterday, possibly when the error was generated. So this time it might be a cache issue ... of database corruption, and in the worst case restarting the system to clear all cached data may help, for now ... out whether a cache is involved or just a bad managed collision. It is also possible (in the optimal

databases are 3 "queue" databases and 3 normal databases). I'm running with the following cache ... lose any benefits of caching around the metadata as soon as a large object is loaded? Are there any ... also the servers, with different configuration (page cache size, query cache size) for the metadata server

.java:591) at com.objectdb.jpa.EMImpl.find(EMImpl.java:514) at com.ysoft. cache .objectdb.ObjectCacheDB.deleteInOpenTransaction(ObjectCacheDB.java:361) at com.ysoft. cache .objectdb.ObjectCacheDB.delete(ObjectCacheDB.java:356) at com.ysoft. cache .objectdb.ObjectCacheDB.delete(ObjectCacheDB.java:347

.java:686) at com.ysoft. cache .objectdb.ObjectCacheDB.search(ObjectCacheDB.java:522) at com.ysoft. cache

.jpa.JpaQuery.getResultList(JpaQuery.java:686) at com.ysoft. cache .objectdb.ObjectCacheDB.search(ObjectCacheDB.java:522) at com.ysoft. cache .objectdb.ObjectCacheDB.search(ObjectCacheDB.java:496) at ysoft

.class); bensteele Ben Steele Maybe it was a cache problem and restarting the database cleared the cache

. For example, the  EntityManager may not be aware that a cached entity object in its persistence ... its synchronization with the database. For example, the  EntityManager may not be aware that a cached

) at com.ysoft. cache .objectdb.ObjectCacheDB.search(ObjectCacheDB.java:522) at com.ysoft. cache .objectdb