You can calculate the time that it takes for an LDAP search to complete by comparing debug message timestamps in the ObjectServer log file. You can use the log entries to see how long individual searches take and to optimize the order of the searches in your queries.
In the following log file extract, multiple distinguished names were specified for the search.
2013-02-07T09:20:25: Debug: D-AUT-105-005: About to issue LDAP search with filter '(cn=User Five)' and base dn 'ou=Webtop,ou=Tivoli,ou=SWG,o=ibm'
2013-02-07T09:20:25: Debug: D-AUT-102-006: No LDAP user found with base dn 'ou=Webtop,ou=Tivoli,ou=SWG,o=ibm' and filter '(cn=User Five)'
2013-02-07T09:20:25: Debug: D-AUT-105-005: About to issue LDAP search with filter '(cn=User Five)' and base dn 'ou=OMNIbus,ou=Tivoli,ou=SWG,o=ibm'
2013-02-07T09:20:25: Debug: D-AUT-105-004: LDAP search on user 'User Five' returned distinguished name 'cn=User Five,ou=OMNIbus,ou=Tivoli,ou=SWG,o=ibm'
The ObjectServer searched for the user name User Five, as specified by the LDAPSearchFilter property in the LDAP properties file. The base distinguished name for the search, as specified by the LDAPSearchBase property, was ou=Webtop,ou=Tivoli,ou=SWG,o=ibm;;ou=OMNIbus,ou=Tivoli,ou=SWG,o=ibm. The ObjectServer searched for each distinguished name in the order given. The search on the Webtop base distinguished name failed.
The total search time is the difference between the timestamps of the first and last log entries (in this case, less than one second). The difference between the timestamps of the first and second log entries gives the time taken for the failed Webtop search.