8.8.1 Linux Hardware Requirements#
Hardware requirements depend on the specific implementation of eDirectory. Two factors increase performance: more cache memory and faster processors. For best results, cache as much of the DIB Set as the hardware allows.
eDirectory scales well on a single processor. However, Novell eDirectory 8.8 takes advantage of multiple processors. Adding processors improves performance in some areas — for example, logins — and having multiple threads active on multiple processors also improves performance. eDirectory itself is not processor intensive, but it is I/O intensive.
The following table illustrates typical system requirements for eDirectory for Linux:(From the DOCS)
| Objects | Processor | Memory | Hard Disk |
|---|
| 100,000 | Pentium III 450-700 MHz (single) | 384 MB | 144 MB |
| 1 million | Pentium III 450-700 MHz (dual) | 2 GB | 1.5 GB |
| 10 million | Pentium III 450-700 MHz (2 to 4) | 2+ GB | 15 GB |
My Recommendations
| Objects | Processor | Memory | Hard Disk |
|---|
| 100,000 | Pentium IV 3gHz(single) | 2 GB | 2 GB |
| 1 million | Pentium IV 2gHz (dual) | 2 GB | 5 GB |
| 10 million | Pentium IV 2gHz (2 to 4) | 2+ GB | 50 GB |
Sizing Overview#
Memory#
As far as I know, eDirectory is a 32bit application and therefore can only use 2GB of RAM. The 2GB is for eDirectory itself above any other processes and OS requirements on the disk. So if you run iManager, that is above and beyond the eDirectory usage.
eDirectry Memory sizing is dependent mainly on:
- The size of the database cache.
- Simultaneous LDAP searches that return large volumes of data also take up some memory (up to 200 KB for each simultaneous request).
- As the number of objects increase in the directory,so does the requirement of memory. For example,100,000 objects in the directory would require a minimum of 384MB of RAM, whereby 1 million objects would require a minimum of 2GB of RAM.
Storage#
- eDirectory uses database blocks of 4KB in size, by default. For optimum update performance,the file system block size should match the database block size an the DIB.
- Disk striping gives significant performance throughput for update operations. For optimum update performance, the DIB should be stored on a stripe volume the more spindles the better.
- We have seen significant improvements using fast NAS/SAN devices as the IO wait states from the OS are much lower.
Disk Space Requirements#
Keep in mind:
- DIB space requirements is usually small. We see 100 MB of disk space for 50,000 users working fine.
- eDirectory administration utilities take some space depending on which are installed.
8.8.1 System Requirements#
- One of the following:
- OES Linux SP2 32 bit
- SUSE Linux Enterprise Server 8.x 32 bit
- SUSE Linux Enterprise Server 9 32 bit (SP1, SP2 & SP3) and 64 bit (SP3) or later
- SUSE Linux Enterprise Server 10 32 bit and 64 bit
NOTE: eDirectory 8.8 SP2 is supported on SLES 10 XEN virtualization service that runs
the SLES 10 guest OS. The following updates are available at https://update.novell.com
(https://update.novell.com).
- SUSE-Linux-Enterprise-Server-X86_64-10-0-20061011-020434
- SLES10-Updates
For registering and updating SUSE Linux Enterprise 10, refer to Registering SUSE Linux
Enterprise 10 with the Novell Customer Center (http://support.novell.com/techcenter/articles/RegandUpdate_SLE10.html). After installating the latest update, ensure that the
minimum patch level of the installed update is 3.0.2_09763-0.8.
To determine the version of SUSE Linux you are running, see the /etc/SuSE-release file.
Red Hat Enterprise Linux ES & AS 3.0 32 bit#
Ensure that the latest glibc patches are applied from Red Hat Errata (http://rhn.redhat.com/errata) on Red Hat systems. The minimum required version of the glibc library is version 2.1.
- Red Hat Enterprise Linux AS 4.0 32 and 64-bit
- 256 MB RAM minimum
- 90 MB of disk space for the eDirectory server
- 25 MB of disk space for the eDirectory administration utilities
- 74 MB of disk space for every 50,000 users
- Ensure that gettext is installed
NOTE: By default, gettext is not installed on the base install of SLES9, but is included in the SLES9 install CD's. Ensure you install it before you run nds-install, or you will get messages about it missing.
There might be more information for this subject on one of the following: