Internal Website Search
1-50 of 185 resultsWorking with JPA Entity Objects Entity objects are in- memory instances of entity classes (persistable user defined classes ... context is to make sure that a database entity object is represented by no more than one in- memory ... . Therefore, a database object can be represented by different memory entity objects in different | |
Out of memory; lwalkowski Lukasz Walkowski Some new data. After 5 hours of running database memory usage is quite high ... thing is - allocated memory by storage threads stops at the size of database. Maybe there is some ... to analyze the memory consumption. Currently it seems that most of the heap space is in use for various | |
Index causes increased memory usage is consuming MUCH more memory (~8gb instead of ~3gb) than when the indices are not included. What could be taking up that memory ? The data load was the same for both tests ... up all the memory on the server? Thanks, CVTSC cvtsc Dev Team Using indexes should not make | |
Memory leak while merging parent with No Cascade annotation with children Hello support, While tracking memory leak in my application i suspected a memory leak in the merging object db implementation. The test case is the following, just run and watch the " Memory Used" by ... ; for (int n=0;n No memory leak })   | |
in-memory and on-disk support? looking at replacing a setup of H2 where I have 40GB in- memory backed by 800GB on-disk, the 40GB in memory represents the first 40GB of the 800GB on-disk for super-fast recent entry searching, the records at the end continuously purge as the new ones come in(duplicate write, one to in- memory | |
High memory consumption even after close() of EntityManagerFactory Hello, we still have memory usage problems. When debugging, we have now observed a case in ... with which you can observe similar behavior. The huge memory usage only occurs if we execute the query (line 56 to 61). If we remove this query, all is well. The memory is only released after we re-run | |
Inserted entities with strings as keys and indices needs more and more ram memory in comparing to primitive integers as keys and indices of further entities needs also more and more ram memory , this leads to out of memory exceptions. But if use primitive integers as keys and indices then the memory consumption for new entities is constant ... and indices needs only more ram memory , but not more and more memory . And if the max heap memory is big | |
Object DB In memory : without Filestore completely in Memory ? (without any writes to Disk, it's okay to loose the data if the node is down ). I ... the Object DB completely in memory without disk storage. thanks, Sandeep Sandeep Sandeep Dhamale At the moment, ObjectDB doesn't support pure in memory mode, but it still can be used completely in | |
Server closes if large query runs out of memory;the objectdb server can run out of memory and stop if a query deals with too many objects. This isn't ... , and so should be able to fail safely if it finds too many objects being retrieved to fit into memory . There must be some alternative to crashing! If this memory estimate is too crude for some people | |
Memory Leak in EntityManagerFactory ? Hi While trying to improve our server with profiler I've encoutered some memory issues that I ... and removed from memory (checked in the Profiler) 4. nevertheless there are lots of identical Copies of Entities in the memory ( QPtBearbeiter in the example). There are only 8 entities of QPtBearbeiter in | |
Intermittent Server Shutdowns Due to Out of Memory (OOM) Issues is frequently being terminated by the Linux Out-Of- Memory (OOM) Killer. Despite allocating substantial memory resources to the server (90GB total memory on the VM), the java process hosting ObjectDB is being killed due to exceeding memory limits. Here are the specifics of my setup and the issue: Server | |
Suspected memory leak Hi, We are running soak testing with Object DB and it is showing signs of memory leak: used memory ... memory dump next time this happens. In the meantime, could you please check if there is anything wrong ... open memory leak issue in ObjectDB. But if it is not something in your application (such as | |
Need help to analyse very high memory usage by objectdb (PRU, SEV, VAL[]) Hello, we have a useCase in which we consume too much memory and run into a "GC overhead limit exceeded" exception. Nearly 90% of the memory are taken by com.objectdb.o.PRU (49%) com.objectdb.o.SEV (29%) and com.objectdb.oVAL [] (9%). When debugging, we did not get the reason for the high memory | |
Memory Leaks after COMMIT operation (checked on versions 2.6.5 & 2.6.6.b01) During import big logs we are observed some memory leaks inside of ObjectDb, so, could you explain what we did incorrectly or investigate how to fix it ASAP. Source code which causing memory leaks ... above (write a 10-15 Mbytes) need to check remaining memory in any available profiler. Stack trace | |
In memory processing for ObjectDB, but to take it to next level really we wanted to check whether is there any In memory mode available ... have a all of my Objects in Cache ? We can run the embeeded mode for perfomance, or embeeded + in memory ... You can use ObjectDB in a pure in memory mode by using a RAM drive . However, high performance | |
Memory consumption of empty Strings After doing some memory related research in my program, I found a possible place ... are empty (""). To avoid unnecessary memory consumption, the String within the entities ... object, which is a waste of memory (refer to http://www.cs.virginia.edu/kim/publicity/pldi09tutorials | |
Is there an update on running ObjectDB purely in-memory? ObjectDB purely in- memory , without a any file on disk? Note that "file on RAM disk ... - memory mode, as supported by SQL databases like H2 or SQLite. Thanks, David dbb David Blumenthal-Barby ... version 2.6.4. In the configuration you can define suffixes that indicate memory only databases:   | |
Performance and memory usage of queries requires so much memory . In the implementation of our UnitTests we have used "DELETE FROM Object" to delete the database. That did not work because we often get an "out of memory " exception. What's all done in the execution of queries? Why is so much memory is required, although from the application point | |
Memory error during commit, if @ElementCollection field contains many elements. But this one runs into memory error and happens only, if we have many elements in the element collection ... a memory error? btc_es BTC EmbeddedSystems When an entity object (such as a TCStep instance ... content still requires memory space. Lazy setting in JPA is considered as a hint | |
Run out of memory the uncommitted changes persist in RAM (not the file db), hence I am getting out of memory exceptions ... frees memory at the EntityManager (client side in C/S mode), but the ObjectDB storage engine (server side in C/S mode) still keeps the changes in memory until commit. As a result, the transaction size | |
Memory leak Hi, We have a memory leak in our application which seems to be related with ObjectDB. Basically ... and after execution of query. Our classes are enhanced with ObjectDB enhancer. However, used memory is growing ... % of memory , even after performing GC from the JVisualVM (screenshots in the attachment). Heap dump | |
How to track memory leak with ObjectDb. Hello, I suspect some memory leak in my application. ( turning app into OOM very fast ) In fact ... ( with Eclipse MAT ), i was not able to inspect carrefully the memory leak issue ... inside objectdb.MST containing some trace of my entities beans. It seems objectdb keep in memory some | |
Warmup ( preLoad all table rows into memory ) Hi , I have 3 questions for objectdb : 1-) How can i preload all table rows into memory in objectdb ? So i can query fast. I have seen @Cacheable annotation. But i need warmup table to memory ... ; eix128 Kadir BAŞOL How can i preload all table rows into memory in objectdb ? You will have to run | |
Memory use in OneToMany relationships all Instances of B into Memory when we query for A. Example: Class Pet holds ... more data about that picture. If we assume we load 10 Pet from the DB into memory and assume each Pet has 10 Pictures would that mean that we automatically load 100 byte[]'s worth of pictures into memory | |
Retrieving JPA Entity Objects extreme situations this might cause the retrieval of the entire database into the memory ... the entire graph of objects is present in memory . This illusion, which is based on lazy transparent ... the refresh method: em. refresh (employee); The content of the managed object in memory is discarded | |
Database Schema Evolution of an old schema is loaded into memory it is automatically converted into an instance of the up to date entity class. This is done automatically in memory each time the entity object is loaded. The database | |
Database Explorer stores String instances in the database using the same encoding that they have in memory , which is usually Unicode. If you store in the database String instances that have a different memory | |
Locking in JPA of the in- memory object being updated. The transaction fails and an OptimisticLockException is thrown ... that e1 and e2 are two in- memory entity objects that represent one database object | |
Database Connection using JPA within these boundaries are associated with that transaction and are kept in memory until the transaction is ended ... . However, by default, the in- memory instance of the managed entity is not affected by the rollback | |
Index Definition system rather than in memory . The keys of the BTree are all the unique values in the indexed field (or arrays of values | |
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 | |
JPA Class Enhancer is checked and automatically enhanced in memory (if applicable). Notice, however, that only classes | |
Storing JPA Entity Objects. The combination of the clear and flush methods can be used to save memory in large transactions: em. getTransaction (). begin (); for (int i = 1; i | |
Obtaining a JPA Database Connection content, such as persist and remove . Database updates are collected and managed in memory and applied | |
FROM clause (JPQL / Criteria API) that all the database objects are available in memory for navigation. But this feature | |
SELECT clause (JPQL / Criteria API) less memory . SELECT DISTINCT Queries that use projection may return duplicate results. For example | |
General Settings and Logging The configuration element specifies ObjectDB settings that are relevant to both the server side and the client side. The default configuration file contains the following element: The element To meet memory constraints ObjectDB can use temporary files when processing large data | |
Database Management Settings engine settings: The cache attribute is a hint that specifies the amount of memory that is used | |
Server out of memory exceptions I've started to get memory exceptions on objectdb instances running as a server. The objectdb log ... of where the memory is being used. In each exception case the server has typically been running for 3-4 days ... . Could you get heap dump snapshots - after one day, two days, three days - in order to detect memory leakage | |
Memory leak in com.objectdb.o.CST Hi. I am pretty sure this is something I did wrong. I have a memory leak ... , will it be normal that these instances are in memory even if entity manager is closed ... ; But if the size can get even bigger, I need to know what affects it so I don't run out of memory | |
Out of Memory - Slow leak? the meantime I've attached the leak suspects report from Eclipse Memory Manager in the hope it may help ... themselves!) felixobjectdb Richard Szurgot The fix of issue 61 fixed an important memory leak but unfortunately it seems that it is not the only one. Hopefully the new memory leak can also be fixed after exploring the heap | |
Large query parameter - out of memory. After about 300 queries the test throws an out of memory exception so I assume the query data is being held ... behind the test is to create a data cache to prevent the need for large data to be held in memory . The data ... cached query result size. Since Java doesn't provide information on heap memory size of data | |
GC Memory Hi there, I was hoping to get some support on ObjectDB regarding memory usage. I received ... ;The process then loads each segment file into memory and then calls persist on each object.   ... too many large objects in one transaction. Note that only commit can release memory , not flush | |
[ODB1] Chapter 6 - Persistent Objects Objects Persistent In JDO applications, every object in memory is either a persistent object, i.e ... the database, its no-arg constructor is used to construct a memory object to represent ... before, persistent objects are memory objects that represent some content in the database | |
[ODB1] Chapter 9 - ObjectDB Explorer more than 64MB of memory . If you need to run the Explorer with increased available memory , you can use the -Xmx ... , constructing objects, editing fields, defining roots, etc.) are stored in memory , associated ... the database using the same encoding that they have in memory , which is usually Unicode. If you store | |
[ODB1] Chapter 2 - A Quick Tour object database, can simply store a memory data structure in the database as is. If the database is not ... the database when the transaction is committed (line 37). Note: Memory objects that represent database ... ) are automatically stored in the database. Objects in memory that are reachable from persistent | |
[ODB1] Chapter 3 - Persistent Classes of persistent classes that live only in memory ) are called transient objects or transient instances ... , which enables transparent use of old schema instances. When an old instance is loaded into the memory ... , it is stored using the new schema. Until then, the conversion is done only in memory each time | |
[ODB1] Chapter 5 - JDO Connections with that transaction and are kept in memory until the transaction is ended. If the transaction is ended ... are only performed in memory (they are never propagated to the database). javax.jdo.option.RetainValues | |
[ODB1] Chapter 8 - ObjectDB Server, you can increase the maximum allowed memory and instruct Java to run in server mode in order | |
[ODB1] Chapter 7 - JDOQL Queries memory , and for requerying the result of a previous JDOQL query. A query can also be executed |