ObjectDB Database Search

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

.setFlushMode(FlushModeType.COMMIT); //q.setHint(QueryHints. CACHE _USAGE, CacheUsage

(bypassing OS cache ). This should prevent any possible data loss of committed transactions. support Support

sec and 2.8 sec. On 'hot' db file  without query result in cache , execution time is between

, threads, query- cache , memory usage, etc...) to use for tuning b. Show all database connections

to the EntityManager metamodel for caching some oft-used information in an application-wide

@Inheritance(strategy=InheritanceType.JOINED) // Success for Inheritance Sonsection //@ Cache (size=10000

cache , but unfortunately it is unclear how this happened. support Support We get this exception

are removed from the cache and then retrieved again, fixing the broken relationship). When using a short

features:     Virtualization:         AMD-V Caches (sum of all):  

); } } nullcrud N J It seems to work as expected. The entity object is cached in the EntityManager  as

of the profiler. First i thought it might be the L2 Cache or something simular but then i could not understand

a cache of loggers keyed to classes for lookup: public final class LoggerWrapper extends

My questions is about : 1-) Can objectdb server handle 200.000+ connections at the same time concurrently ? Does it have queue and cache ? 2-) is it dangerous to use that system on many online users ?   kadirbasol Kadir BASOL Having 200,000 concurrent threads is probably a bad idea. Usually

cache bug. Fixed several bugs in query processing and running. It is highly recommended to run

+reload. Thanks. lo Hoel Maybe you should try disabling all sorts of cache in the configuration file

. Everything works fine now. Seems that maven had cached some old jar. mosi0815 Ralph Moser

we have a customer system with 64 GByte RAM, 16 CPUs on 8 sockets, the fastest possible ssd. we wonder if the cache and other settings can be optimized to get the most performance these are the current settings, please advice what we could optimize hgzpincher Hans-Georg Zwicker

itself doesn't alter the database, by rolling it back after I've generated the views. Your caching probably

;  //Close everything and reopen to make sure no cache of the description / code is left

my code block :     @CacheEvict("loginsList")     @Transactional     default int updateUserEnabled(Boolean enabled , Integer sicilNo, Cache loginCache) {         Optional bySicilNoOptional = findBySicilNoOptional(sicilNo);      

, it appears this issue is an internal bug related to how cached pages are stored in temporary files

.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

Improved performance of collection and map size evaluation in queries. Fixed a critical bug in page caching (issues #610 , #621 , #625 ). Fixed a bug in optimization of non ASCII string indexes. Fixed the new query HOUR function to return hours as 0 to 23 (using 24-hour clock). Fixed a regression

unspecific (any query that normally takes some ms). Could there be a problem somewhere in the cache

of this query fells to 1457 on repeating runs (when cache is disabled), will be checked now

ObjectDB database files are usually smaller than database files of other Database Management Systems (object databases and relational databases) but additional internal compression is still possible. Usually smaller files are also faster because less I/O operations are required and memory cache

the object is retrieved again from the database (and not from the persistence context cache ), or

BTC EmbeddedSystems The stack trace indicates an unexpected state of the query result cache

, and on complete clean and build in NetBeans, and also after complete NetBeans cache clear

Hello , it will be good if you make alliance with terra-cotta ehcache. Their distributed memory cache is very fast.IF we mix with your engine. It will be very great for us. kadirbasol Kadir BASOL

instead of Long ) and then updated. Fixed retrieval with pessimistic lock to bypass cache and to force refresh.

cache InternalException. Fixed JDO PersistenceManager 's  newObjectIdInstance to support classes

class. Fixed a query cache bug. Fixed several bugs in query processing and running. Fixed a query

Added support of report generation using BIRT . Fixed a bug in query optimization of DISTINCT. Fixed a bug in keeping removed entity object in the L2 cache . Fixed orphan removal of owner entity object in bidirectional relationship. Fixed an "Attempt to persist a reference to a non managed instance

.getResultList(JpaQuery.java:686) at com.ysoft. cache .objectdb.ObjectCacheDB.search(ObjectCacheDB.java:433

activation key. Maybe your activation server is broken? skolb Sebastian Kolb Maybe it is a cache

the first entry (required by Apache Karaf ). Fixed a cache bug in repeating some sorts of LIKE queries