Poor performance of People Directory and logins
First attempt to load People directory is very slow, while consecutive loads are faster (because Confluence cached the result). Logins are also slow.
If you have defined your <baseusernamespace> in a high level of the LDAP tree and <usersearchalldepths> property is set to true, this combination is a recipe for slowness in accessing the People directory - at least during the initial search (as you have set the LDAP caching to true).
Splitting the <LDAP> entries will create an adverse effect to your performance as noted in Configuring Multiple LDAP Repositories. This is not preferred.
The solution is to implement a better user search filter. If you have an LDAP browser tool, you can test that your filter is correct via the tool (for example in Apache Directory Studio click on the
LDAP > New Search menu, then fill in the new value for your filter. You can also tune the LDAP Cache.
For more references on LDAP in our documentation, please have a look at: