# LDAP performance issues

For performance reasons, the LDAP directory server should be in the same LAN as Derby. Derby does not cache the user's credential information locally and thus must connect to the directory server every time a user connects.

Connection requests that provide the full DN are faster than those that must search for the full DN.

Parent topic: Configuring LDAP authentication
Related concepts
Booting an LDAP server
Setting up Derby to use your LDAP directory service
Guest access to search for DNs
LDAP restrictions
JNDI-specific properties for external directory services