Service manual

Types of Cache
110 Sun ONE Directory Server Installation and Tuning Guide • June 2003
Actual memory used by the Directory Server process depends primarily on the
memory allocation library used, and on the entries cached. Entries with many
small attribute values usually require more overhead than entries with a few large
attribute values.
For 32-bit servers, entry cache size must in practice be limited to 2 GB or less.
Refer to the Sun ONE Directory Server Reference Manual for further details
concerning the valid range of
nsslapd-cachememsize and nsslapd-cachesize
values.
Import Cache
The import cache is created and used during suffix initialization only, also known
as bulk loading or importing. If the deployment involves offline suffix initialization
only, import cache and database cache are not used together, so you need not add
themtogether when aggregatingcachesizeasdescribedin“TotalAggregate Cache
Size.” You specify import cache size (
nsslapd-import-cachesize). Changes to
import cache size take effect the next time the suffix is reset and initialized, with
import cache allocated for the initialization, then released after the initialization.
Directory Server handles import cache as it handles database cache. Ensure
therefore that sufficient physical memory is available to prevent swapping.
For 32-bit servers, import cache size must in practice be limited to 2 GB or less.
Refer to the Sun ONE Directory Server Reference Manual for further details
concerning the valid range of
nsslapd-import-cachesize values.
NOTE On AIX platforms, DirectoryServer is created with
maxdata =
0x50000000
, allowing you to allocate 1 GB each to both database
cache and entry cache. Contact your Sun ONE support
representative if you must change the value of
maxdata.