In order to address a wide range of deployments and configurations, two mechanisms for controlling the cache memory consumption are provided in the eDirectory. These mechanisms are mutually exclusive.
You can specify a hard memory limit in one of the following ways:
As a fixed number of bytes.
As a percentage of physical memory.
As a percentage of available physical memory.
When a hard limit is specified by using the second or third method, it is always translated to a fixed number of bytes. This means that for the second method, the number of bytes is the percentage of physical memory detected when eDirectory is started. For the third method, the number of bytes is the percentage of available physical memory detected when eDirectory is started.
A dynamic adjustment causes eDirectory to periodically adjust its memory consumption in response to the variable memory consumption by other processes. Although adjusting memory dynamically works well in typical scenarios, this mechanism is not recommended for optimal performance of eDirectory on Linux platforms because of large differences in memory usage patterns and memory allocators on Linux platforms.