Tuning a directory server for performance

Edit online

You must tune a directory server instance to improve the search and update performance.

You can run Configuration Tool or the idsperftune command to tune a directory server instance. The tool generates performance tuning setting values for the directory server caches and DB2® buffer pools. The tool generates the tuning settings that are based on the values that you provide about the directory server instance. The tool can also update the tuning settings for an instance. The tool backs up the ibmslapd.conf file and saves it in the logs/ibmslapd.conf.save file in the home directory for a directory server instance.

The tool saves the information that you provide in the perftune_input.conf file in the home directory for a directory server instance.

Configuration Tool or the idsperftune command uses the values that you provide to calculate the following tuning settings for the instance:

  • Entry cache size
  • Filter cache size
  • Group Member Cache size
  • Group Member Cache Bypass Limit
  • DB2 LDAPDB buffer pool size
  • DB2 IBMDEFAULTDB buffer pool size

If your directory server instance is running, the tool monitors the performance of the instance and provides the database health check information. The database health check information includes the following DB2 parameters:

  • DB2 NUM_IOSERVERS
  • DB2 NUM_IOCLEANERS
  • CATALOGCACHE_SZ
  • PCKCACHESZ
  • LOGFILSIZ
  • LOCKLIST

If you run advanced tuning on an instance, the tool collects and analyzes data about the directory server instance. You must run the instance for some time to collect DB2 tuning data during the database health check analysis. The tool generates the tuning values for the following DB2 parameters and saves them in the logs/perftune_stat.log file for the instance.

  • SORTHEAP
  • MAXFILOP
  • DBHEAP
  • CHNGPGS_THRESH
  • NUM_IOSERVERS
  • NUM_IOCLEANERS

The health status suggestions for the DB2 parameters can be one of the following values:

  • OK
  • Increase
  • Decrease
  • Not Collected

The health status of DB2 parameters that are not analyzed is assigned the Not Collected value. You can use the suggested values to decide the DB2 parameters that you can tune to obtain better performance.

For better performance, you must run the tool on an instance as soon as you load the initial directory data. After the initial tuning, run the tool periodically especially after you add many entries or modify the content of entries.For more information about tuning a directory server instance, see the Performance Tuning and Capacity Planning section in the IBM® Verify Directory documentation.

You cannot use Configuration Tool or the idsperftune command to tune a proxy server instance or an instance that is not configured with a database.