Poor LDAP Performance

We have 2 Domino LDAP servers. Both were running with Domino 5.0.11 and Windows 2000. Recently (as part of an upgrade project) one was upgraded to Domino 6.5.4 and Windows 2003. This server is now so slow that we cannot direct LDAP traffic to it. Windows 2003 SP1 has been applied in an attempt to improve performance, but this has had no effect. I’ve also been experimenting with the nlcache_size setting in NOTES.INI, but this also appears to have had minimal impact.

These servers are not used by clients to perform address lookups, but are used by a proxy server to authenticate users wishing to access the internet.

Does anyone have any ideas? Before we have to consider a down-grade back to R5.0.11…

Many Thanks,

Phil

Subject: Poor LDAP Performance

Philip, Have you tried deleting and recreating the names.nsf FT index?:-jmw

Subject: Poor LDAP Performance

Please contact IBM support for help with this issue. Is LDAP serving up names.nsf only or is it serving up more than one book? If the answer is “more than one”, then I’m sure support will want to know if you’re using cascaded address books, or if you have Directory Assistance configured.

One thing that you can do to get some helpful diagnostic information is to turn on the INI “LDAPDEBUG=7”. You can do this on both your R5 server and your V6 server, then do an identical LDAP search to each server and see if there’s any difference in what search filter is being sent in. Copy the debug to an e-mail and annotate it when you send it to support… they’ll really appreciate that.

Just a side-note… the “Cascaded Address Books” feature has been deprecated for 6.0 and above.

+Josh+