11 | Objectdb server out of heap space. support Support I'm well aware of VM options for tuning memory. A server process |
11 | Lazy Init / Eager / Join Fetch collection strategy ? What to choose ? for every situation, so you will have to test these options in your specific scenario to tune your application |
11 | Processing thread count for 8-core server the range of 15-30 threads, but choosing the best value will require some tuning tests on your side, since it depends on the specific application. support Support |
11 | Index causes increased memory usage). Is there some sort of tuning we can do to have both fast queries and not soak up all the memory |
11 | On ensuring ID available after persist commit to ObjectDB I can then adopt performance tuning strategies that suit it better, such as TABLE. webel Dr Darren Kelly |
11 | How Should I Configure objectdb.conf to Obtain 256KB Disk IO Requests and Maximize Shared PersistenceManager Entity Cache? (e.g. searching for an object in a larger page could take longer). So, as with most tuning |
11 | Speed of queries that return many objects, although with enhancement and tuning it could be in the range of 1-2 seconds. The overhead of preparing entity |
11 | Object DB vs EclipseLink/TopLink: Unloaded relationships in detached entities properties This has the big problem that one would need to tune queries for every preempted |
2 | out of memory error space). Increasing the JVM heap size could solve the problem, or alternatively, tuning ObjectDB |
2 | Best practise loading big data the database (i.e. the EntityManagerFactory). If you need an advice regarding tuning cache sizes |
