LDAP-UX Integration Performance and Tuning Guidelines

will help and administrator to set the cache_size parameter. Following is the sample output of

/opt/ldapux/bin/ldapclientd –s . Administrator can set cache size according to first two entries from the

statistics. mem_in_use and high_mark_mem gives good idea of how much memory is being used right at that

moment and highest level at the memory has reached so far.

$ /opt/ldapux/bin/ldapclientd -s

mem_in_use ............ 40281

high_mark_mem ......... 47719

cache_hits_pos ........ 117

cache_hits_neg ........ 16

cache_reqs ............ 1325

cache_entries ......... 314

cache_pos_entries ..... 312

cache_neg_entries ..... 2

cache_reload .......... 1

high_mark_ent ......... 371

queued high ........... 1

queued ................ 0

% Improved

0204060

+ve/-ve cache_ttl

in seconds

% of improvement

% Improved

In testing performed at HP performance was improved up to 30 % by setting the +ve /-ve cache_ttl to

higher period of time. Result may vary according to different environments. Above table assumes active

clients. If you have inactive clients larger cache_ttls will be required to reduce the load on the server

further.

SSL Support on LDAP-UX Integration product.

B.03.20, the latest version of LDAP-UX integration product supports Secure Socket Layer (SSL). SSL is the

mechanism that LDAP-UX will provide secure communications between the HP-UX client and the directory server.

SSL protects both data and passwords transmitted by clients over the network. As a result of adding SSL to the

product the ldapclientd caching daemon is now a required in order to support LDAP-UX operation, where before it

was optional.

Page 9