IBM Security Directory Server, Version 6.3.1

The performance tuning tool input file

To tune a directory server with the idsperftune command, you must update the perftune_input.conf property file with the configurable values.

The perftune_input.conf property file contains a list of inputs for the idsperftune command in the form attribute-value pairs. To update the perftune_input.conf file, you must log in with directory server instance owner credentials. If you do not want to specify values for the attributes, then you must leave the values as None.

You must update the attribute values as per your requirements, and then run the tool by providing the property file as an input. You must ensure that the attribute names are not modified in the property file. If the attribute names are modified, the idsperftune tool generates an appropriate error message and exits. On AIX®, Linux, and Solaris systems, the perftune_input.conf file is in instance-home/idsslapd-inst_name/etc. On Windows system, the perftune_input.conf file is in instance-location\idsslapd-inst_name\etc. The format of an example perftune_input.conf file is as follows:

#------------------------------------------------------
#Admin Input
#------------------------------------------------------
# Amount of system memory (%) to be allotted to TDS instance 
TDS_SYS_MEM=90
# Total number of entries that will reside in the directory
TDS_TOTAL_ENTRY=10000
# Average size of entry (Bytes)
TDS_AVG_ENTRY_SZ=2560
# Update Frequency 
#1. Frequent updates expected, or
#2. Only Batch Updatesexpected
TDS_UPDATE_FREQ=1
#Total number of Groups to be cached
TDS_GROUP_CACHE=25
# Maximum number of members in a group that will be referenced frequently
TDS_GROUP_MEMBER=25000
#
#-------------------------------------------------------
# DB2 PARAMETER INPUT 
#-------------------------------------------------------
# NEWLOGPATH allows you to specify a string of up to 242 bytes to change 
# the location where the log files are stored. Eg, NEWLOGPATH=”/newdevice”
NEWLOGPATH=None
# LOGFILSIZ defines the size of each primary and secondary log file. The size 
# of these log files limits the number of log records that can be written to 
# them before they become full and a new log file is required.
LOGFILSIZ=None
# DBHEAP determines the maximum memory used by the database heap.
DBHEAP=None
# PCKCACHESZ is allocated out of the database shared memory, and is used for 
# caching of sections for static and dynamic SQL and XQuery statements on 
# a database.
PCKCACHESZ =None
# LOGBUFSZ allows you to specify the amount of the database heap (defined 
# by the dbheap parameter) to use as a buffer for log records before writing 
# these records to disk.
LOGBUFSZ=None
# MAXFILOP specifies the maximum number of file handles that can be open 
# for each database agent.
MAXFILOP=None
# CHNGPGS_THRESH specifies the level (percentage) of changed pages at which 
# the asynchronous page cleaners will be started, if they are not currently active.
CHNGPGS_THRESH=None
# SORTHEAP defines the maximum number of private memory pages to be used 
# for private sorts, or the maximum number of shared memory pages to be 
# used for shared sorts.
SORTHEAP=None


Feedback