Internal Website Search

which has max performance at that size and reduces monetary fees by having fewer accesses). max performance at that size and reduces monetary

enabled="true" sync="false" path="." max="128mb" />   <recording enabled="false" sync ... ;processing cache="1024mb" max-threads="8" />   <query-cache results="1024mb" programs

I'm trying to replicate a database using the following config: <server>   <connection port="6136" max="100" />   <data ... -config"> <server> <connection port="6138" max="100" /> <data path="$objectdb/db

cases if instead of specifying first/max results you will add a constraint in each iteration based ... could be more efficient in some cases if instead of specifying first/max results you will add

enabled="true" sync="true" path="." max="128mb" />     <recording ... -check="true" />     <processing cache="64mb" max-threads="10" />

) INFO: Created EjbThreadPoolExecutor with thread-core-pool-size 16 thread-max-pool-size 32 thread ... EjbThreadPoolExecutor with thread-core-pool-size 16 thread-max-pool-size 32 thread-keep-alive-seconds 60 thread-queue

" sync="false" path="." max="128mb" /> <recording enabled="false" sync="false" path="." mode="write" /> <locking version-check="true" /> <processing cache="64mb" max-threads

;           <recovery enabled="true" sync="false" path="." max="128mb ... ;processing cache="64mb" max-threads="10" />              

; <recovery enabled="true" sync="false" path="." max="128mb" /> <recording enabled ... ;processing cache="8mb" max-threads="10" /> <query-cache results="0mb" programs="500" />

" max="1000000" /> Starting 2.6.5 the client gets an exception but the server continues to work as expected and max="0" (which is the default starting 2.6.5) indicates no limit. support Support