 2 | if you have millions of objects. Currently the workaround is to use queries with max results limit. Viewing all the objects of a class without a query and max result limit is not a common feature in database viewers |
2 | ="false" path="." max="128mb" /> max-threads="10" /> |
2 | |
2 | (Thread.java:722)
INFO: Created EjbThreadPoolExecutor with thread-core-pool-size 16 thread-max-pool ... -size 16 thread-max-pool-size 32 thread-keep-alive-seconds 60 thread-queue-capacity 2147483647 allow |
2 | packet requests to the datastore file (because it is stored on an Amazon EBS disk which has max ... (because it is stored on an Amazon EBS disk which has max performance at that size and reduces monetary |
2 | .conf file:
max="0" />
max="0" /> |
2 | " resize="500mb" page="2kb" />
max="128mb ... " />
max-threads="10" />
|
2 | could be more efficient in some cases if instead of specifying first/max results you will add ... loop could be more efficient in some cases if instead of specifying first/max results you will add |
2 | Hello, I have question regarding objectdb recovery when objectdb is not finished correctly (power outage). We are using following configuration:
max ... ="true" sync="true" path="." max="128mb"/> This setting guarantees that every invocation of commit |
2 | one running JBOSS and other running ObjectDB. - CPU utilization of JBOSS server is max 5-10 ... . For example: - CPU utilization of JBOSS server is max 5-10% (per core) - CPU utilization of JBOSS server is 80 |