SUMMARY
System Under Test (SUT) | Oracle's SPARC T5-2 server | ||
Software | Oracle Internet Directory 11gR1-PS6 | ||
Target Load | 50 million user entries | ||
Reference URL | OID/T5 benchmark white paper | ||
Oracle Internet Directory (OID) is an LDAP v3 Directory Server that has multi-threaded, multi-process, multi-instance process architecture with Oracle database as the directory store.
BENCHMARK WORKLOAD DESCRIPTION
Five test scenarios were executed in this benchmark - each test scenario performing a different type of LDAP operation. The key metrics are throughput -- the number of operations completed per second, and latency -- the time it took in milliseconds to complete an operation.
TEST SCENARIOS & RESULTS
1. LDAP Search operation : search for and retrieve specific entries from the directory
In this test scenario, each LDAP search operation matches a single unique entry. Each Search operation results in the lookup of an entry in such a way that no client looks up the same entry twice and no two clients lookup the same entry, and all entries are looked-up randomly.
#clients | Throughput Operations/Second | Latency milliseconds |
---|---|---|
1,000 | 944,624 | 1.05 |
2. LDAP Add operation : add entries, their object classes, attributes and values to the directory
In this test scenario, 16 concurrent LDAP clients added 500,000 entries of object class InetOrgPerson with 21 attributes to the directory.
#clients | Throughput Operations/Second | Latency milliseconds |
---|---|---|
16 | 1,000 | 15.95 |
3. LDAP Compare operation : compare a given attribute value to the attribute value in a directory entry
In this test scenario, userpassword attribute was compared. That is, each LDAP Compare operation matches user password of a user.
#clients | Throughput Operations/Second | Latency milliseconds |
---|---|---|
1,000 | 594,426 | 1.68 |
4. LDAP Modify operation : add, delete or replace attributes for entries
In this test scenario, 50 concurrent LDAP clients updated a unique entry each time and a total of 50 million entries were updated. Attribute that is being modified was not indexed
#clients | Throughput Operations/Second | Latency milliseconds |
---|---|---|
50 | 16,735 | 2.98 |
5. LDAP Authentication operation : authenticates the credentials of a user
In this test scenario, 1000 concurrent LDAP clients authenticated 50 million users.
#clients | Throughput Operations/Second | Latency milliseconds |
---|---|---|
1,000 | 305,307 | 3.27 |
BONUS: LDAP Mixed operations Test
In this test scenario, 1000 LDAP clients were used to perform LDAP Search, Bind and Modify operations concurrently.
Operation breakdown (load distribution): Search: 65%. Bind: 30%. Modify: 5%
LDAP Operation | #clients | Throughput Operations/Second | Latency milliseconds |
---|---|---|---|
Search | 650 | 188,832 | 3.86 |
Bind | 300 | 87,159 | 1.08 |
Modify | 50 | 14,528 | 12 |
And finally, the:
HARDWARE CONFIGURATION
1 x Oracle SPARC T5-2 Server » 2 x 3.6 GHz SPARC T5 sockets each with 16 Cores (Total Cores: 32) and 8 MB L3 cache » 512 GB physical memory » 2 x 10 GbE cards » 1 x Sun Storage F5100 Flash Array with 80 flash modules » Oracle Solaris 11.1 operating system |
ACKNOWLEDGEMENTS
Major credit goes to our colleague, Ramaprakash Sathyanarayan