For production , sometimes we modify entities.
We use this config on production for 128GB Ram server its too low ?
with 48 Core
How to increase performance more ?
Also chatgpt suggested to use this for auto update entities but when i add it , it crashes.
ObjectDB doesnt let these params :
<objectdb>
<property name="objectdb.h2f" value="auto"/>
<property name="objectdb.schema.auto" value="true"/>
</objectdb>
<objectdb>
<general>
<!-- Keep logs small and fast -->
<temp path="$temp/ObjectDB" threshold="128mb" />
<network inactivity-timeout="0" />
<url-history size="100" user="true" password="true" />
<log path="$objectdb/log/" max="16mb" stdout="true" stderr="false" />
<log-archive path="$objectdb/log/archive/" retain="120" />
<logger name="*" level="error" />
</general>
<database>
<!-- Small pages give more granular caching; larger ones reduce overhead -->
<size initial="1mb" resize="512kb" page="4kb" />
<recovery enabled="true" sync="false" path="." max="256mb" />
<recording enabled="false" sync="false" path="." mode="write" />
<locking version-check="true" />
<processing cache="256mb" max-threads="16" synchronized="true" />
<query-cache results="128mb" programs="2000" />
<extensions drop="temp,tmp" />
<activation code="xxxx-xxxx-xxxx-xxxx-xxxx" />
</database>
<entities>
<!-- Strong cache keeps entities in memory until eviction -->
<enhancement agent="true" reflection="warning" />
<cache ref="strong" level2="512mb" />
<persist serialization="false" />
<cascade-persist always="auto" on-persist="false" on-commit="true" />
<dirty-tracking arrays="true" />
</entities>
</objectdb> Tuning and making reliable for server
#1
#2
These settings do not appear to exist (likely a ChatGPT hallucination).
128 GB should be sufficient as long as your database is smaller than that.
To optimize performance, you’ll need actual profiling data.
ObjectDB Support
