DIRECTORY SERVICES


Using performance settings in a condensed Directory Catalog
Directory catalog performance settings in the Advanced tab of a configuration document for a condensed Directory Catalog are "Packing density" -- that is, how many source IBM® Lotus® Domino™ Directory entries can be combined in one directory catalog aggregate document -- and "Incremental fields" -- that is, how and when the Dircat task updates changes to fields in the aggregate documents. The default directory catalog performance settings work fine in most situations.

Note Change these settings only on a condensed Directory Catalog used only by servers, and not on a condensed Directory Catalog used by clients.

These settings are irrelevant and unavailable for an Extended Directory Catalog which doesn't combine multiple source Domino Directory entries into aggregate documents.

Packing density

The packing density is the number of entries from a source Domino Directory that can be stored in one aggregate document in the condensed Directory Catalog. 255 is the maxium packing density and the default. If full-text searching is frequently used to search a server directory catalog, for example if the LDAP service uses the directory catalog, and these searches of the directory catalog are slow, you can decrease the packing density to improve performance of these searches.You might also decrease the packing density to reduce the odds that a particular aggregate document needs to replicate.

Incremental fields

Because a single field in an aggregate document contains values for the field from many of the source Domino directories, it's likely that at any one time every field in the aggregate document might require updating and, therefore, would need to replicate. To manage changes to fields in a condensed Directory Catalog, the Dircat task, by default, uses an incremental merge process that stores the changes in temporary fields in aggregate documents until, by default, 5 percent of the total entries from the source Domino Directories change. Then the Dircat task merges the changes stored in the temporary fields into the permanent fields in the aggregate documents and deletes the temporary fields. This process occurs somewhat randomly over a period of time so that at any time, only a few aggregate documents need to replicate. When the directory catalog on the server running the Dircat task replicates, only the updated fields replicate. This incremental replication results in improved replication performance, especially when replication occurs over a dial-up connection.

The alternative to incrementally merging fields is to make changes as they occur directly in the original fields in aggregate documents. Disabling incremental merging provides some modest gains in search performance. However, if replication with the source Directory Catalog occurs over dial-up connections, keep incremental merging enabled.

Next to the Incremental fields option in a configuration document for a condensed Directory Catalog, Choose Yes (the default) to use incremental merging and temporarily store field changes in duplicate fields in aggregate documents to optimize replication performance. Or choose No to immediately makes changes in the original fields in the aggregate documents.

Merge factor

The Merge factor option in a configuration document for a condensed Directory Catalog is a value representing the percent of total field changes that must occur before Domino merges the changes stored in duplicate fields into the original fields in aggregate documents; default is 5 percent.

This field applies only when "Incremental fields" is set to Yes.

Note It is not recommended that you change this setting.

See also