
PERFORMANCE STUDY /8
VMware vCloud Director 1.0 Performance and Best Practices
LDAP Sync
vCloud Director supports importing users and groups from external LDAP servers. An external LDAP server is
one that is not part of the cloud that vCloud Director manages. When a LDAP user logs in, the vCloud Director
server checks if the necessary information for this user has been loaded. If the user is not loaded, vCloud Director
issues a LDAP search request to fetch the user information. In addition to checking and fetching user information,
the sync process also includes the removal of records for users who have been deleted in an external LDAP
server.
LDAP Sync Latency for Different Numbers of Users
LDAP sync in vCloud Director is implemented with a single thread. All LDAP users are updated in a sequential
manner. This approach ensures the resource consumption is small when a LDAP sync task runs a background job
within the vCloud Director server.
In our tests, we observed that, as the number of users increases, latency increases. Figure 3 gives you an idea of
what amount of LDAP sync latency to expect for the number of LDAP users on your system.
Figure 3. LDAP Sync Latency in Seconds for 1000, 3000, and 10,000 LDAP Users
0
20
40
60
80
100
120
140
160
0 2000 4000 6000 8000 10000 12000
Latency in Seconds
Number of Users
Commentaires sur ces manuels