administration mode

Performance Peek blog

Domino LDAP Performance »

CHRISTIAN DENCKER - JAN 16, 2015 (07:03:04 PM)

Performance optimization

To allow the Domino LDAP severs handle the load coming through the LDAP protocol from Sametime Community Servers, at least the following steps should be followed on the Domino LDAP servers:

 

Indexing

Every address book available in the Domino LDAP must be full text indexed.(FTI)

Cache

Domino LDAP cache is disabled by default. It must be manually enabled in notes.ini on the Domino LDAPs:


LDAP_QRCACHE_SIZE=268435456
NLCACHE_SIZE=268435456

For Domino LDAPs with lots of RAM which are dedicated for Sametime, the size can be set higher:

LDAP_QRCACHE_SIZE=536870912
NLCACHE_SIZE=536870912

Domino LDAP server must be restarted for the changed to take affect.

Note that only hits are added to the Domino LDAP cache. Searches that don't find a match in the cache slow the LDAP greatly, meaning that the number of searches unmatched in the Directory should be as minimal as possible. The ways to achieve this are discussed in the “Optimizing Sametime searches performance” section.


Number of worker threads
Domino LDAP uses 40 worker threads by default for handling LDAP requests. The number should be raised to 80 in notes.ini:

LDAPMaxWorkerThreads=80

For Domino LDAPs with lots of RAM which are dedicated for Sametime, the size can be set higher:

LDAPMaxWorkerThreads=120

Domino LDAP server must be restarted for the changed to take affect.

DA.nsf considerations
Unnecessary secondary address books pointed by DA.nsf on the Domino LDAP servers must be removed from DA.nsf or be disabled for LDAP searches.