JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Directory Server Enterprise Edition Deployment Planning Guide 11g Release 1 (
search filter icon
search icon

Document Information


Part I Overview of Deployment Planning for Directory Server Enterprise Edition

1.  Introduction to Deployment Planning for Directory Server Enterprise Edition

2.  Business Analysis for Directory Server Enterprise Edition

Part II Technical Requirements

3.  Usage Analysis for Directory Server Enterprise Edition

4.  Defining Data Characteristics

5.  Defining Service Level Agreements

6.  Tuning System Characteristics and Hardware Sizing

Host System Characteristics

Port Numbers

Directory Server and Directory Proxy Server LDAP and LDAPS Port Numbers

Directory Server DSML Port Numbers

Directory Service Control Center and Common Agent Container Port Numbers

Identity Synchronization for Windows Port Numbers

Hardware Sizing For Directory Service Control Center

Hardware Sizing For Directory Proxy Server

Configuring Virtual Memory

Configuring Worker Threads and Backend Connections

Disk Space for Directory Proxy Server

Network Connections for Directory Proxy Server

Hardware Sizing For Directory Server

The Tuning Process

Making Sample Directory Data

What to Configure and Why

Directory Server Database Page Size

Directory Server Cache Sizes

Directory Server Indexes

Directory Server Administration Files

Directory Server Replication

Directory Server Threads and File Descriptors

Directory Server Growth

Top Tuning Tips

Simulating Client Application Load

Directory Server and Processors

Directory Server and Memory

Directory Server and Local Disk Space

Directory Server and Network Connectivity

Limiting Directory Server Resources Available to Clients

Limiting System Resources Used By Directory Server

Operating System Tuning For Directory Server

Operating System Version and Patch Support

Basic Security Checks

Accurate System Clock Time

Restart When System Reboots

System-Specific Tuning With The idsktune Command

File Descriptor Settings

Transmission Control Protocol (TCP) Settings

Physical Capabilities of Directory Server

Other Tips to Improve Overall Performance

Tuning Cache Settings

Basic Tuning Recommendations

For Maximum Search Rate (Searches Only)

For Maximum Modification Rate (Modifications Only)

Small, Medium, and Large Data Sets

Optimum Search Performance (Searches Only)

Optimum Modify Performance (Modifications Only)

Tuning Indexes for Performance

Basic Directory Server Sizing Example: Disk and Memory Requirements

System Characteristics

Preparing a Directory Server Instance

Populating the Suffix With 10,000 Sample Directory Entries

Populating the Suffix With 100,000 Sample Directory Entries

Populating the Suffix With 1,000,000 Sample Directory Entries

Summary of Observations

7.  Identifying Security Requirements

8.  Identifying Administration and Monitoring Requirements

Part III Logical Design

9.  Designing a Basic Deployment

10.  Designing a Scaled Deployment

11.  Designing a Global Deployment

12.  Designing a Highly Available Deployment

Part IV Advanced Deployment Topics

13.  Using LDAP-Based Naming With Solaris

14.  Deploying a Virtual Directory

15.  Designing a Deployment With Synchronized Data


Tuning Indexes for Performance

The use of indexes can enhance performance by reducing the time taken to perform a search. However, indexes also have an associated cost. When an entry is updated, the indexes referring to that entry must also be updated. The more an entry is indexed, the more resources are required to update the index; indexes take up disk space and memory space.

When you design indexes, ensure that you offset the benefit of faster searches against the associated costs of the index. Maintaining useful indexes is good practice; maintaining unused indexes for attributes on which clients rarely search is wasteful.

You can optimize performance of searches in the following ways:

To prevent Directory Server from performing searches on non-indexed entries, set the require-index-enabled suffix property for the suffix.

To limit the number of values per index key for a given search you can set an index list threshold. If the number of entries in the list for a search key exceeds the index list threshold, an unindexed search is performed. The threshold can be set for an entire server instance, for an entire suffix, and for an individual attribute type. You can also set individual thresholds for equality, presence, and substring indexes.

For a detailed procedure on how to change the index list threshold, seeChanging the Index List Threshold in Oracle Directory Server Enterprise Edition Administration Guide. This procedure modifies the all-ids-threshold configuration property.

The global value of all-ids-threshold for the server instance should be about 5% of the total number of entries in the directory. For example, the default value of 4000 is generally right for instances of Directory Server that handle 80 000 entries or less. You should avoid setting the threshold above 50 000, even for very large deployments. However, you might set all-ids-threshold to a value other than the 5% guideline in the following situations:

You should limit the number of unindexed searches that are performed. Use the logconv utility provided with the Directory Server Resource Kit to examine the access logs for evidence of frequent unindexed searches. For more information, see the logconv(1) man page.