HP-UX Directory Server Administrator Guide HP-UX Directory Server Version 8.1 (5900-3098, May 2013)

1. Select the LDBM Plug-in Settings tab in the right pane.
This tab contains the database attributes for all databases stored on this server.
2. In the Maximum Cache Size field, enter a value corresponding to the amount of memory to
make available for all databases.
3. In the Look-Through Limit field, enter the maximum number of entries for the server to check
in response to a search request.
4. In the Import Cache Size field, enter a value corresponding to the amount of memory in bytes
to make available for import. By default, the value is auto, and 50% of the free memory is
allocated for the import cache. For creating a very large database from LDIF, set this attribute
as large as possible, depending on the memory available on the machine. The larger this
parameter, the faster the database is created.
To keep from setting a limit, type -1 in this text box. If a user binds to the directory as the
Directory Manager, by default the look-through limit is unlimited and overrides any settings
specified here.
To configure the attributes of each database that stores the directory data:
5. In the Directory Server Console, select the Configuration tab; then, in the navigation tree,
expand the Data Icon. Expand the suffix of the database to tune, and highlight the database.
The tabs displayed in the right pane control parameter settings for this database.
1. Select the Database Settings tab in the right pane.
2. Enter the amount of memory to make available for cached entries in the Memory Available
for Cache field.
16.2.2 Tuning transaction logging
Every Directory Server contains a transaction log that writes operations for all the databases it
manages. Whenever a directory database operation such as a modify is performed, the server
logs the operation to the transaction log. For best performance, the directory does not perform the
operation immediately. Instead, the operation is stored in a temporary memory cache on the
Directory Server until the operation is completed.
If the server experiences a failure, such as a power outage, and shuts down abnormally, the
information about recent directory changes that were stored in the cache is lost. However, when
the server restarts, the directory automatically detects the error condition and uses the database
transaction log to recover the database.
Although database transaction logging and database recovery are automatic processes that require
no intervention, it can be advisable to tune some of the database transaction logging attributes to
optimize performance.
CAUTION:
The transaction logging attributes are provided only for system modifications and diagnostics.
These settings should be changed only with the guidance of HP Professional Services or HP Technical
Support. Setting these attributes and other configuration attributes inconsistently may cause the
directory to be unstable.
16.2.3 Changing the location of the database transaction log
By default, the database transaction log file is stored in the
/var/opt/dirsrv/slapd-instance_name/db directory along with the database files
themselves. Because the purpose of the transaction log is to aid in the recovery of a directory
database that was shut down abnormally, it is a good idea to store the database transaction log
on a different disk from the one containing the directory database. Storing the database transaction
log on a separate physical disk may also improve directory performance.
To change the location of the database transaction log file, use the following procedure:
540 Tuning Directory Server Performance