ObjectDB Database Search

.mendix.com/link/ space /app-development/questions/7625 (old link) https://stackoverflow.com/questions ... to run DB Doctor because of the space required for a temp file on C:\.   Is there a way

that may cause this error and the result is free space that is not reclaimed but no other known consequences, the space   can be reclaimed by fixing the database with the Doctor

is needed. How many such objects do you have? What is the total space that they consume (check in ... the database contains? How much spaces these classes consume (out of the 64GB, you can check it in

Doctor to handle additional issues. Improved query execution planner. Improved cleanup and reusing space

part of the containing entity. Since there is no separate space allocation for the collection or its elements

, cheers, and thank you in advance,   Alan alacalcas Alan Alan, Wow so i just spaced

they are mainly used to save space and improve performance. In many cases queries will run faster

persisting a new one (this could also save space in the database). Split the query - first find the relevant

closely at 'src-java ' where the error icon is - it seems that you have an extra  space

ObjectDB consumes much less space than the same data in a JPA/RDBMS combination. support Support

: Java heap space at com.objectdb.o.SBT.readArray(SBT.java:156) at com.objectdb.o.ART.readStrictly

byte[] by reducing required storage space . Removed a shutdown hook that leads to memory leak ( issue

the space that the index takes, but it is only required after adding new indexes. support Support

a... java.lang.OutOfMemoryError: Java heap space This is after the db crunches for about 20s or

Hi, Few days ago I was writing some code to iterate over quite a large dataset. Fitting those data in memory was quite a challenge even with 3GB heap space . So I did paging using two loops. for (int page=0; page

' (or what objectDB calls the space to save entities), called 'MetaClass'. And so apples and oranges

with 2800 records) throws a "java.lang.OutOfMemoryError: Java heap space " exception. Emil prolancer Emil

(which is forbidden, since every EntityManager manages its own space of managed objects, and a managed

, since every EntityManager manages its own space of managed objects, and a managed object of one EntityManager should not

It seems that there is a bug in logging mechanism, if you try to start the database which is already started it starts filing the log continuously until it runs out of space on disk. How to check is the database runing from command promt. regards.   peric.emil Emil Perić This is caused by

, and it is also more efficient, since numbers are more efficient than strings (take less storage space

server and not for the slave server. To save space please try limiting recording to write operations

we get: Exception in thread "Thread-30" java.lang.OutOfMemoryError: Java heap space at java.util

ObjectDB database, in order to make space for new entity? Thank you in advance for any answer. Best Regards

Hello, I suspect some memory leak in my application. ( turning app into OOM very fast ) In fact, some com.objectdb.o.MST objects are retaining a huge % of my heap space . While watching the dump file ( with Eclipse MAT ), i was not able to inspect carrefully the memory leak issue

more space (i.e. more database pages), which means more work to manage it, and possibly harder to cache

of Java heap space in any scenario. Regarding a query that returns too many objects, consider

an entity object. This could be efficient it terms of space and retrieval speed but may be more expansive in

storage space , etc.) so this is expected. If you are concerned because you have to repeat

(as you save a lot of small allocations and space for references), not just in persisting to the database. support Support

without database schema change, and save some space in memory. You can still use StringIdentity

Hi, I want to drop one column from my database table suppose i have 3 column (id, name, address) now i want to drop address. then what will be the query or procedure..   Bimal Bimal kumar dalei Just remove the field from the entity class. See Automatic Schema Evolution . Space in the database

to the index (on the left side) will usually decrease performance due to a larger index space

, however, that internally ObjectDB identifies simpler date/time instances, such as in your question, and their storage consumes less space . support Support

. If it is "all" you can save a lot of space (and improve performance) by switching to the "write" mode

Hello, we have issue with online-backup when using client-server mode. It seems, that it is working the following way. When we run the backup, server is creating tmp file for whole database and then copying it to the target location. So it takes twice as long and consumes twice storage space

). Still, this can be a nice to have feature in some applications. support Support Our company works in the healthcare space

from last start - caches hit rate - total sessions from clients - memory usage (for heap space

cleanup and reusing space after index deletion. Changed default configuration (enabled recovery

). Improved persisting byte[] by reducing required storage space . Removed a shutdown hook that leads

it, thus to get space for another one. Currently, we are not able to do that, which is frustrating. We're

could be to store many large objects and then to delete them, creating more space and avoiding resizing

again. The database file is corrupt. I checked the HDD for errors but there are none. The disk space

space limitations. Why the entity DBVectorStepBlockCollectionImpl is still hold by ObjectDB? Best

, which has a separate space . Apparently the new build changed the exception from the one in #3 above to 

database space after removing an index. Improved error message on attempt to enhance a class in a jar

) at 80% average - SSD, around 100 GByte free space , no significant/bad latency or queue

your application and consumes a lot of disk space , so it is unclear if it is applicable

Added support of Java 8 date and time types (issues #1495 ,  #2564 ). Added information in the Explorer on consumed database space ( feature request #2540 ). Fixed handling enum types that implement interfaces in the Explorer ( Issue #2542 ). Improved memory cleaning when entity objects

for very large queries) the connections in the pool hold unreasonable memory space . Please try build 2