Red Hat Directory Server 7.1 Performance Tuning and Sizing Guidelines

Overview

Product Overview

Red Hat Directory Server for HP-UX provides an industry standard centralized directory service to build your intranet or extranet on. Your directory-enabled applications use the directory service as a common, network- accessible location for storing shared data such as user and group identification, server identification, and access control information. In addition, you can extend the Red Hat Directory Server to support your entire enterprise with a global directory service that provides you with centralized management of all your enterprise's resource information.

Purpose of This Document

This document provides basic sizing and performance tuning guidelines for Red Hat Directory Sever (RHDS) version 7.1 for HP-UX 11i v2 on Integrity Server. It also provides the performance test results of RHDS 7.1 on HP- UX Integrity (IA64) Servers. The RHDS 7.1 is a 64-bit Directory Server.

The data provided here is intended to help system and network administrators to effectively size and tune different directory server configurations. Some major topics such as class of machines, amount of memory, and number of CPUs are covered. This document also covers how to tune some of the key performance related attributes for RHDS.

Please keep in mind that data presented in this document are measured under controlled environment. Testing for these guidelines were performed on dedicated HP-UX servers connected by private LAN. No other system activities were running during the performance testing. For RHDS version 7.1 performance test details, see Appendix A.

Sizing and Tuning Overview

Hardware

The following sizing guidelines should be used when selecting a system to use as a Red Hat Directory Server. They are discussed in more detail in Section “Sizing Guidelines”.

•Any HP IA64 architecture with an Intel® Itanium 2 processor or Intel® Itanium 2 dual core processor can be used for Red Hat Directory Server.

•When correctly tuned, the eventual performance bottleneck will be CPU.

•At least 256 MB of memory is required. However, you should plan from 512 MB to 4 GB or more of RAM for best performance on large directories. As an example, if your directory contains 250K entries where the average entry size in entrycache is 3860 bytes, and if your directory server only needs to support exact search requests on the “cn” attribute, you might want to have at least 2.5 GB of memory available for the directory server to cache all the information needed.

•Approximately 251 MB of disk space for a minimal installation (without loading any user data) is required. For production systems, you should plan at least 2 GB to support the product binaries, databases, and log files (log files require 1 GB disk space by default). As an example, for a directory instance with 250K entries and average entry size on disk is 700 bytes, it requires the minimum of 0.9 GB disk space for database, default index files and minimum logging (access log is turned off).

Page 1