Hardware Requirements

For optimal performance, your system must have sufficient RAM memory for the JVM heap and database cache. For more information on setting the JVM heap and database cache, see Configuring the JVM, Java Options, and Database Cache.

On Solaris systems, the operating system should be configured to have at least twice as much virtual memory as JVM heap. To achieve this, you might need to increase the size of the operating system swap space.

Your system should also have enough disk space to store the generated log files. The server log files can consume up to 1 Gbyte of disk space with default server settings. In replicated environments, the change log database can grow up to 30-40 Gbytes with loads of 1000 mods/sec. For information on setting log file size, see Managing Administration Traffic to the Server in Sun OpenDS Standard Edition 2.2 Administration Guide.

You can configure Sun OpenDS Standard Edition in such a way that it uses substantially less, or more, disk space depending on your application and performance needs. Any setup considerations must determine the amount of memory for the server's database and log files.

As a general guideline, the following hardware is recommended:

Hardware Component

Requirement

RAM

Evaluation purposes: At least 256 Mbytes of free memory for a small database.

Production: Minimum of 2 Gbytes.

If you are using a global index catalog, you might need more memory. Typically, you should have 20 Gbytes of RAM for every 100,000,000 entries that are stored in the global index catalog.

Note - For large databases or large global index catalogs that require more than 4 Gbytes of RAM, your system should use 64–bit architectures.

Local disk space

Evaluation purposes: For a small database and sufficient space for log files, your system should have at least 100 Mbytes of free local disk space. Preferably, you should have at least 1 Gbyte of disk space.

Production: For a typical production deployment with a maximum of 250,000 entries and no binary attributes, such as images, 4 Gbytes of disk space might be sufficient for the database only. You might need an additional 1 Gbyte of disk space for log files. You need to determine disk space for the change log database (DB), which is dependent on the load (updates per second) and on the replication purge delay (that is, the time the server should keep information about internal updates). The change log DB can grow up to 30-40 Gbytes with loads of 1000 modifications per second.

When you use global index replication, ensure that you have enough disk space for the replication change logs. By default, the change log stores changes from the last 24 hours. The configuration should be based on the expected size of the service. For example, you would need 150 Gbytes for 5000 modify/seconds.

Note - The directory server does not support databases and logs installed on NFS-mounted file systems. Sufficient space should be provided for the database on a local file system, for example, in /var/opt or /local on UNIX or Linux machines.

Exit Print View
Sun OpenDS Standard Edition 2.2 Installation Guide