Summary of Contents for Novell EDIRECTORY 8.8 SP5 - TUNING GUIDE FOR UNIX 12-02-2009
Page 1
AUTHORIZED DOCUMENTATION Tuning Guide for UNIX* Platforms Novell ® eDirectory 8.8 SP5 December 02, 2009 www.novell.com Novell eDirectory Tuning Guide for UNIX* Platforms...
Page 2
Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Page 3
Novell is a registered trademark of Novell, Inc., in the United States and other countries. Novell Client is a trademark of Novell, Inc. Novell Directory Services and NDS are registered trademarks of Novell, Inc., in the United States and other countries.
Page 4
Novell eDirectory Tuning Guide for UNIX* Platforms...
® A trademark symbol ( , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. When a single pathname can be written with a backslash for some platforms or a forward slash for other platforms, the pathname is presented with a backslash.
Page 6
Novell eDirectory Tuning Guide for UNIX* Platforms...
Overview Novell® eDirectory 8.8 is a standards-compliant, cross-platform, highly scalable, fault-tolerant, and high-performance directory services solution. This guide provides information on tuning your eDirectory environment for improved performance. Tuning for performance is a complex activity. It requires understanding of both the eDirectory and operating system's subsystems.
Page 10
However, it is important to understand the security implications (http://www.novell.com/documentation/nmas33/admin/ index.html?page=/documentation/nmas33/admin/data/bg8dphs.html). health checks (http://www.novell.com/documentation/edir88/edir88/data/a5ziqam.html) through iMonitor. Ensure the following: Time is in sync across all replica servers. Replica synchronization and background processes are in a healthy state. Novell eDirectory Tuning Guide for UNIX* Platforms...
eDirectory Subsystems This section discusses the eDirectory Subsystems. Section 2.1, “FLAIM Database,” on page 11 Section 2.2, “Thread Pool,” on page 12 2.1 FLAIM Database eDirectory uses FLAIM as its database. FLAIM (Flexible Adaptable Information Manager) is used for traditional, volatile, and complex information. It is a very scalable database engine that supports multiple readers and a single-writer concurrency model.
It is inefficient and costly to frequently create and destroy threads. Instead of spawning new threads Novell eDirectory Tuning Guide for UNIX* Platforms...
Page 13
and destroying them for every task, a number of threads are started and placed in a pool. The system allocates the threads from the thread pool to several tasks as needed. Tasks are held in two types of queues: Tasks that need immediate scheduling are held in the Ready queue. Tasks that need scheduling at a later time are held in the Waiting queue.
Page 14
Novell eDirectory Tuning Guide for UNIX* Platforms...
Analyzing System Bottlenecks There are several system resources that influence eDirectory performance. In addition, upgrading to the latest version of operating system improves performance. Section 3.1, “Disk I/O Subsystem,” on page 15 Section 3.2, “CPU Subsystem,” on page 16 Section 3.3, “Memory Subsystem,” on page 16 Section 3.4, “Network Subsystem,”...
The maximum memory that can be allocated to a process is limited in several ways. A certain amount of RAM is used by the operating system and other processes on the system. The operating system can impose limitations on physical RAM that a process uses. For example, a 32-bit Novell eDirectory Tuning Guide for UNIX* Platforms...
eDirectory limits the FLAIM cache to 2.5 GB, but with 64-bit eDirectory, FLAIM caches can grow beyond 2.5 GB. However, the 64-bit eDirectory needs an increased memory footprint (approximately 20%) than the 32-bit eDirectory. 3.4 Network Subsystem Typical deployments have sufficient bandwidth to handle peak network load. Adequate bandwidth reduces errors, collisions, and dropped packets.
Page 18
Novell eDirectory Tuning Guide for UNIX* Platforms...
Tuning eDirectory Subsystems This section includes the following information: Section 4.1, “FLAIM Database,” on page 19 Section 4.2, “Thread Pool,” on page 20 Section 4.3, “ACLs,” on page 21 Section 4.4, “Replication,” on page 23 Section 4.5, “SSL Overhead,” on page 24 Section 4.6, “64-Bit Versus 32-Bit,”...
If the number of tasks in the Ready queue is high and increasing. Keep increasing the max threads if the performance of the server increases. It should also result in increased CPU utilization. Novell eDirectory Tuning Guide for UNIX* Platforms...
By default, an ACL is not marked as read filtered, so the performance benefit for requests to return all attributes is not seen. The following table depicts the location of arf_acl.ldif and rrf_acl.ldif files in different platforms. Platform Location UNIX /opt/novell/eDirectory/lib/nds-schema/ NetWare <unzipped_location>\nw\sys\system\schema Windows <unzipped_location>\nt\I386\NDSonNT\ndsnt\nds Tuning eDirectory Subsystems...
2 In the output noted in the previous step, delete the information marked in bold. 3 Save the revised output as an LDIF file. 4 Add the following information to the newly saved LDIF file: dn: cn=schema changetype: modify delete: objectclasses objectclasses: (2.16.840.1.113730.3.2.2) add:objectclasses Novell eDirectory Tuning Guide for UNIX* Platforms...
Synchronization can be avoided by using DIBClone (http://www.novell.com/documentation/edir88/edir88/data/acavuil.html#aky13ak), which allows cloning a server with the same partitions. By default, in eDirectory, the maximum number of synchronization threads is set to 8. The maximum allowed value is 16.
4.6 64-Bit Versus 32-Bit Because of the increased size of some of the basic data types in 64-bit eDirectory environments, it needs an increased memory (approximately 20%) over the same instance of 32-bit eDirectory. Novell eDirectory Tuning Guide for UNIX* Platforms...
FLAIM cache. 4.7 Import Convert and Export (ICE) The Novell Import Convert and Export (ICE) utility uses an optimized bulk update protocol called LBURP to upload data into eDirectory. This protocol is significantly faster than uploading data by using a simple command.
Page 26
Novell eDirectory Tuning Guide for UNIX* Platforms...
eDirectory Configuration This section includes the following information: Section 5.1, “Configuring the FLAIM Subsystem,” on page 27 Section 5.2, “Modifying FLAIM Cache Settings,” on page 27 5.1 Configuring the FLAIM Subsystem In order to address a wide range of deployments and configurations, two mechanisms for controlling the cache memory consumption are provided in the eDirectory.
5.2.1 Modifying FLAIM Cache Settings through iMonitor You can use iMonitor to do the following: View or change the cache settings. Monitor the cache statistics. Refer to the Database cache under Agent Configuration of iMonitor for the above information. Novell eDirectory Tuning Guide for UNIX* Platforms...
Database Cache Information Description Maximum Size The maximum size (in KB) that the specified cache is allowed to grow Current Size The current size (in KB) of the specified cache. Items Cached The number of items in the specified cache. Old Versions Cached The number of old versions in the specified cache.
Page 30
- Percentage of the FLAIM cache used for block cache. cacheadjustinterval - Interval in seconds for dynamically adjusting the cache. cachecleanupinterval - Interval in seconds for cleaning up older versions of entries and blocks from the cache. Novell eDirectory Tuning Guide for UNIX* Platforms...