About memory

forum_thread

Server vs embedded mode in multi-instance scenario

We are creating a web app that will have multiple different clients, each on their own EC2 instance(s). The clients do not need to share any data, so each could have its own ObjectDB. Clients have a user base of about 2,000 to 60,000 users that could possibly be using their application at any given time (100k absolute maximum). We will probably have multiple instances per client for availability concerns as well as auto scale during peak usage, at least for the benefit of our web application if not for objectdb.... our webapp stop competing for system resources (cpu time, memory, etc). Is that a valid concern? The graphs on your site would seem to ...

 
release

2.0.3

... a failed find followed by persist. Fixed a memory leakage in eager load of large object graphs. Fixed a ...

 
release

2.0.5

... a failed find followed by persist. Fixed a memory leakage in eager load of large object graphs. Fixed a ...

 
release

2.4.2

... space. Removed a shutdown hook that leads to memory leak ( issue #63 ). Completed missing documentation ... UPDATE & DELETE queries). Fixed memory leak issues. Fixed server hang and deadlock issues. ...

 
release

2.4.1

... space. Removed a shutdown hook that leads to memory leak ( issue #63 ). Completed missing documentation ... UPDATE & DELETE queries). Fixed memory leak issues. Fixed server hang and deadlock issues. ...

 
manual

Working with JPA Entity Objects

Explains the entity object lifecycle and the persistence context. Entity objects are in-memory instances of entity classes (persistable user defined classes), ... entity object is represented by no more than one in-memory entity object within the same EntityManager . Every EntityManager ... a database object can be represented by different memory entity objects in different EntityManager instances. But retrieving ...

 
release

2.0.2

... a failed find followed by persist. Fixed a memory leakage in eager load of large object graphs. Fixed a ...

 
forum_thread

Bidirectional OneToMany is slow on updated items

Hello, I have a problem with the following situation. I insert persons with addresses. In the first run, they are all new with a new address. It runs fast. In the second run, the persons are all loaded and got a second address. This seams to be much slower. The Entities are all enhanced by the javaagent (which you can see in the contained eclipse launch configuration) Is there any way to speed it up?       ... calls of Address and Person instances with an in memory HashMap and get calls. ObjectDB Support ...

 
forum_thread

OutOfMemoryError on search after update on DB created with DB Doctor

It looks like there may be an issue with the DB files created with DB Doctor in recovery mode. This is the scenario that results in the OutOfMemory exception problem (using Object DB 2.5.4_04): 1. We instruct Object DB to create a 1Gb DB file on initial start-up using: <database> <size initial="1024mb" resize="256mb" page="2kb" /> This happens as expected. ... update, any search and CPU use shoots up to > 100% use, memory use shoots up and eventually we get: Exception in thread ...

 
release

2.0.4

... a failed find followed by persist. Fixed a memory leakage in eager load of large object graphs. Fixed a ...