Many users ask how much of memory will be consumed by OrientDB and which settings affects this number. This question becomes even more actual since 2.2 release. In the new release, we allocate memory by big chunks (about of 1Gb size each) and then split it between threads on demand.
So how to calculate the maximum amount of memory which will be consumed by OrientDB ? That is simple. OrientDB uses both memory heap and direct memory. Direct memory is used for the disk cache.
Memory consumed by disk cache may be calculated looking on the value of following configuration parameter
storage.diskCache.bufferSizewhich shows the maximum amount of memory consumed by disk cache in megabytes.
We need to increase this value till it will not be divided to the 1GB without a reminder (size of a chunk of memory allocated by the pool at once).
The rest is easy. Add value which you calculated above and add the amount of memory consumed by memory heap and you will get the maximum amount of memory which will be consumed by OrientDB.
P.S.1 Maximum size of memory chunk in bytes which will be allocated at once by OrientDB may be set using property
P.S.2: You may find actual amount of direct memory consumed by OrientDB accessing properties