Home » Search

About memory

41-50 of 166Refresh
Manual
11

Updating JPA Entity Objects

Modifying existing entity objects that are stored in the database is based on transparent persistence, which means that changes are detected and handled automatically. Transparent Update Once an entity object is retrieved from the database (no matter which way) it can simply be modified in memory
Manual
11

Obtaining a JPA Database Connection

updates are collected and managed in memory and applied to the database when the transaction
Manual
11

JPA / JDO Class Enhancer

with ObjectDB Enhancer as a Java Agent, every loaded class is checked and automatically enhanced in memory
Manual
11

SELECT clause (JPQL / Criteria API)

less memory. SELECT DISTINCT Queries that use projection may return duplicate results. For example
Issue
7

Best practise loading big data

that the memory consumption is extremly high, many elements are hold by internal classes of ObjectDB. Garbage collection does not gain enough free memory. We experimented a bit but so far only workarounds helped to gain a lower memory footprint. One is to stupidly commit the transaction
Issue
4

Use temporary files to enable very large transactions

flush() and detach()). But an array of bytes, any ObjectDB memory, still allocates a lot of memory ... to a temporary file. Even without speed optimizations, but with priority on the memory usage. Ideally ... that can address your needs. Particularly the unlimited size. The memory problem is with Page
Issue
3

stress test -> com.objectdb.o.InternalException: null

, to know how to set the sample. Good/bad news! It seems that Tomee runs out of heap memory ... of memory usage, but using ODB as embedded changes the situation. With a heap of 100 MB, Tomee runs out of memory in ~20 minutes. With a heap of 512 MB, in around 240 min (4 hours). Both cases were tested
Forum
3

Soft Reference Object Cache Recommendation

on the Memory Tab).  Gigabytes of RAM was freed up, and the screenshot shows what did NOT get freed ... the JdoBlob2 via persistenceManager.deletePersisted(jdoBlob2) then the memory gets freed by the next full GC.  I can also close the PersistenceManager and all the memory then can be freed.  I
Issue
3

ODB-FileWriter holds unecessary entity reference after transaction and entity manager are closed

Hello, we've encountered a problem leading to memory leaks. We found that after closing ... the application context. This prevents the garbage collector from cleaning up the memory which eventually results in memory leaks. The attached screenshot shows an example of this behaviour. Thanks
Issue
3

each 1-2 days objects on some objectdb level lock/block each other

.isCurrentOperation is not empty)) the version 03 seems to have a memory leak, we had to shut ... anything on our side, there was no memory leak till that version Running these queries on the database that you sent in a previous ... for that. How can we go on with the improvements ? > the version 03 seems to have a memory leak Sorry to hear. The changes in build 03