eDirectory, the underlying infrastructure for the Identity Vault, is I/O intensive application rather than being processor-intensive. Two factors increase performance of Identity Vault: more cache memory and faster processors. For best results, cache as much of the Directory Information Base (DIB) Set as the hardware allows.
While eDirectory scales well on a single processor, you might consider using multiple processors. Adding processors improves performance in areas such as user logins. Also, having multiple threads active on multiple processors improves performance.
The following table provides a general guideline for server settings, based on the expected number of objects in your eDirectory.
|
Objects |
Memory |
Hard Disk |
|---|---|---|
|
100.000 |
2+ GB (Linux) 384 MB (Windows) |
300 MB (Linux) 144 MB (Windows) |
|
1 million |
4 GB (Linux) 4 GB (Windows) |
1.5 GB |
|
10 million |
4+ GB (Linux) 2+ GB (Windows) |
15 GB |
For example, a base installation of eDirectory with the standard schema requires about 74 MB of disk space for every 50,000 users. However, if you add a new set of attributes or completely fill in every existing attribute, the object size grows. These additions affect the disk space, processor, and memory needed. Also, requirements for processors depend on additional services available on the computer as well as the number of authentications, reads, and writes that the computer is handling. Processes such as encryption and indexing can be processor intensive.