8 | Performance with large databases whenever I run the populating application. Is there typically a database size when indexes can no longer ... the ratio between the database size and the available RAM. As long as the available RAM is larger ... of the JVM heap size and the ObjectDB cache size). Except this, ObjectDB performance should not be affected |
8 | Searching lists within objects.SearchByCustomQuery(query); assertEquals(1, searchResult.size()); query = "SELECT ... ); assertEquals(3, searchResult.size()); query = "SELECT DISTINCT t FROM com ... , searchResult.size()); query = "SELECT DISTINCT t FROM com.contextspace.datamodel.party.CDI t |
8 | Handling "is null" in where clause"); List<EntityA> resultList = query.getResultList(); System.out.println("ResultList size = " + resultList.size()); if (resultList.size() == 0) { throw new Exception("There is no EntityA with simpleField == null ???"); } } ResultList.size() is always 0 |
8 | TYPE Expression(); System.out.println("Size: " + resultList.size()); em.close(); em = emf ... (); System.out.println("Size: " + resultList.size()); em.close(); emf.close |
7 | Index causes increased memory usage% Hopefully this helps? cvtsc Dev Team About 3.5GB are in use by the page cache (which has a size of 64MB per database by default). Have you changed the cache size? A separate cache is managed per open ... open databases with page cache size of 128MB (each) then this explains your numbers. The cache is not |
7 | Possible issue for JPQL IS EMPTY expression IS EMPTY (error 756) Thanks. Note: It doesn' t work with SIZE(): SELECT e FROM MyEntity e WHERE SIZE(e ... IS EMPTY"); System.out.println(query.getResultList().size()); em.close |
7 | Exceeding max connections and crashing are created but not closed. It may also be the result of limited heap size and out of memory errors. Try ... hype size to 6GB and since that we haven’t have any crashes of JBOSS. Important to note is that JBOSS is not on the same server as ObjectDB. After we increased heap size and number of connections 2 days |
7 | in-memory and on-disk support?. Given I have a fixed DB size(800GB) with the need to purge oldest records as new ones come in would it be more optimal to set the <size> element as follows: <size initial="800000mb" resize="0kb |
7 | Externalising persistence.xml properties in Glassfish? the start up script. This is the same place where heap size ect gets set. My other option ... -classname="org.postgresql.ds.PGSimpleDataSource" max-pool-size="20" res-type="javax.sql.DataSource" steady-pool-size="10" description="" name="pgsqlPool"> <property name="User" value="inv_usr |
1 | Tracking changes to new collections (in enhancement mode) after flush ArrayList<>()); list.add("item-" + list.size()); } public int getCount() { return map.get("list").size(); } } } support Support ... : " + entity.list.size()); em.close(); emf.close(); } @Entity |
