eG Help

The most significant setting that affects eDirectory performance is the cache. With eDirectory 8.5 or later, you can specify a block cache limit and an entry cache limit. The block cache caches only physical blocks from the database. The entry cache caches logical entries from the database. The caching of entries reduces the processing time required to instantiate entries in memory from the block cache. The EdirDbCacheTest monitors the block and entry caches of every eDirectory database, and reports whether they are efficiently utilized or not.

Measurement	Description	Measurement Unit	Interpretation
Db_size	Indicates the current size of the eDirectory database	KB
Db_block_size	The current block size of the eDirectory database	KB
Db_entry_current_size	The current entry cache size of the eDirectory database	KB	With an entry cache and a block cache, the total available memory for caching should be shared between the two caches. If the server you are installing eDirectory on does not have a replica, the default is a hard memory limit of 16 MB, with 8 MB for block cache and 8 MB for entry cache. If the server contains a replica, the default is a dynamically adjusting limit. The dynamically adjusting limit causes eDirectory to periodically adjust its memory consumption in response to the ebb and flow of memory consumption by other processes. You specify the limit as a percentage of available physical memory. Using this percentage, eDirectory recalculates a new memory limit at fixed intervals. The new memory limit is the percentage of physical memory available at the time. Along with the percentage, you can set a maximum and minimum threshold. The threshold is the number of bytes that eDirectory will adjust to. It can be set as either the number of bytes to use or the number of bytes to leave available. The minimum threshold default is 16 MB. The maximum threshold default is 4 GB. With the dynamically adjusting limit, you also specify the interval length. The default interval is 15 seconds. The shorter the interval, the more the memory consumption is based on current conditions.
Db_block_current_size	The current block cache size of the eDirectory database	KB
Db_entry_items_cached	The number of entries in the entry cache, currently	Number	An Entry cache is most useful for operations that browse the eDirectory tree by reading through entries, such as name resolution. A well-sized entry cache thus speeds up the retrieval of entries referenced from an index. Therefore, ideally, the value of this measure should be high.
Db_block_items_cached	The number of blocks in the block cache, currently	Number	A well-sized block cache is most useful for update operations and can speed up index searching. A very low number of blocks in this cache could considerably slow-down key eDirectory operations. Therefore, ideally, this value should be high.The more blocks and entries that can be cached, the better the overall performance will be.
Entry_cache_hit_ratio	The percentage of database hits that were served by the entries in the entry cache	Percent	Typically, a 1:1 ratio for block cache, and a 1:2 or 1:4 ratio for the entry cache is desired. Anything lesser indicates that the entry and block caches are unable to fulfill most of the requests to the eDirectory server. This happens when an adequate number of blocks/entries is not cached. Badly-sized caches escalate direct disk accesses and processing overheads as well. The ideal is to cache the entire database in both the entry and block caches, although this is not possible for extremely large databases.
Block_cache_hit_ratio	The percentage of database hits that were serviced by the blocks in the block cache	Percent