Even if you do not need high availability, you still need two of everything, because your test environment needs to mimic your production environment as closely as possible if you want to avoid nasty surprises.
In your test environment, you set up OpenDJ as you will later in production, and then conduct experiments to determine how best to meet the requirements defined in the SLA.
Use make-ldif to generate sample data that match what you expect to find in production.
The OpenDJ LDAP Toolkit provides three command-line tools to help with basic performance testing.
-
The authrate command measures bind throughput and response time.
-
The modrate command measures modification throughput and response time.
-
The searchrate command measures search throughput and response time.
All three commands show you information about the response time distributions, and allow you to perform tests at specific levels of throughput.
If you need additional precision when evaluating response times, use
the global configuration setting etime-resolution to
change elapsed processing time resolution from milliseconds (default) to
nanoseconds.
$ dsconfig set-global-configuration-prop --port 4444 --hostname opendj.example.com --bindDN "cn=Directory Manager" --bindPassword password --set etime-resolution:nanoseconds --no-prompt
For more extensive testing, try the SLAMD Distributed Load Generation Engine. SLAMD is built to test more than just directory, but is particularly well suited to test directory service performance, is well documented, and is available under the Sun Public License. SLAMD is designed both to offer an easy to used web-based interface, and also to allow you to customize jobs to match the access patterns you expect from client applications.
