 2 | works and what is the best way to tune it? Thanks, Natalia. Also, another question about resizing ... resizing works is briefly described in the manual and no other tuning options are currently available |
2 | settings, as normal, the bigger, the better (or are there additional parameters to tune ... always. Unfortunately getting optimal performance requires tuning the configuration to the specific application (e.g |
2 | references for L1 cache (the PersistenceManager) it indeed looks as a JVM tuning issue, because ObjectDB ... . With those, and the additional testing I have been doing, I think the best approach is to use soft references and tune the JVM |
2 | size (if possible) or tune the ObjectDB configuration. If ObjectDB recovery is enabled then ObjectDB |
2 | , threads, query-cache, memory usage, etc...) to use for tuning b. Show all database connections |
2 | .g. searching for an object in a larger page could take longer). So, as with most tuning questions |
2 | is provided on the Query Setting and Tuning page. great, thanks I'd like to know more about this. It looks |
2 | ). Is there some sort of tuning we can do to have both fast queries and not soak up all the memory |
2 | , so you will have to test these options in your specific scenario to tune your application for maximum |
2 | last start - caches hit rate - total sessions from clients - memory usage (for heap space tuning |
