IBM 6.1.X manual Directory Server Tuning, Db2 update db config for idsldap using dbheap

Directory Server Tuning

Our measurements used IBM Tivoli Directory Server versions 6.0 as the directory server. These products use a database for storing user information; DB2 Enterprise Server was used for this database in our environment. This database is typically located on the same system as the directory server. If your workload involves creating, updating, or deleting users, then database maintenance described above may be needed on this database.

The following table shows the tuning values used for the directory servers in our Solaris Base Portal Scenario measurements

How-to-Set:These values are in the file /opt/IBM/ldap/V6.0/etc/SchemaV6.0/ibmslapd.conf. You must restart the LDAP server after changing these values.

Table 9: IDS Tuning

Parameter	Value
Ibm-slapdACLCacheSize	250000
Ibm-slapdEntryCacheSize	250000
Ibm-slapdFilterCacheSize	250000
Ibm-slapdFilterCacheBypassLimit	7500

The IBM Tivoli Directory Server uses IBM DB2 as the database server. The database instance and alias are named IDSLDAP. We applied the following tuning to this database:

db2 “update db config for idsldap using dbheap 4800”

db2 “update db config for idsldap using num_ioservers 10” db2 “update db config for idsldap using num_iocleaners 5” db2 alter bufferpool LDAPBP size 3690

db2 alter bufferpool IBMDEFAULTBP size 88500

2 2

W E BS P HE R E P O R T AL V 6 . 1 T U N I N G G U I D E