Red Hat Directory Server 8.0 Administrator's Guide

link contacts the remote server, forwards the operation, waits for the result, and then sends the

result back to the client application. The entire operation can take much longer than a local

operation.

While the database link waits for results from the remote server, it can process additional

operations. By default, the number of threads used by the server is 30. However, when using

database links, performance can be improved by increasing the number of threads available for

processing operations. While the local CPU waits for a response from a remote server, it can

process other operations rather than stand idle.

To change the number of threads used for processing operations, change the nsslapd-thread

number global configuration attribute in the cn=config entry. Increasing the thread number can

improve performance; the default thread number is 30. Restart the server after changing the

thread count to apply the changes.

3.7. Advanced Feature: Configuring Cascading Chaining

The database link can be configured to point to another database link, creating a cascading

chaining operation. A cascading chain occurs any time more than one hop is required to access

all of the data in a directory tree.

• Section 3.7.1, “Overview of Cascading Chaining”

• Section 3.7.2, “Configuring Cascading Chaining Defaults Using the Console”

• Section 3.7.3, “Configuring Cascading Chaining Using the Console”

• Section 3.7.4, “Configuring Cascading Chaining from the Command-Line”

• Section 3.7.5, “Detecting Loops”

• Section 3.7.6, “Summary of Cascading Chaining Configuration Attributes”

• Section 3.7.7, “Cascading Chaining Configuration Example”

3.7.1. Overview of Cascading Chaining

Cascading chaining occurs when more than one hop is required for the directory to process a

client application's request. For example:

Performance