You can use the perftune_stat.log property file to store the performance values that are suggested by the idsperftune command. Based on the values in the perftune_stat.log file, you must update the values tune a directory server instance.
The information that is gathered during the basic tuning and advanced tuning phases are logged in the perftune_stat.log property file. The log file provides what action to take on a DB2® parameter value to get better performance from the directory server. On AIX®, Linux, and Solaris systems, the perftune_stat.log file is in instance-home/idsslapd-inst_name/logs. On Windows system, the perftune_stat.log file is in instance-location\idsslapd-inst_name\logs.
A sample perftune_stat.log file is generated from a directory server instance on a Linux system. The directory server is loaded with entries from the /opt/ibm/ldap/V6.3.1/examples/sample.ldif file.
The format of a sample perftune_stat.log file is as follows:
#------------------------------------------------------
# Perftune Basic tuning parameters
#------------------------------------------------------
#------------------------------------------------------
# Directory Cache
#------------------------------------------------------
TDS_ENTRY_CACHE=1000
TDS_FILTER_CACHE=0
TDS_GROUP_CACHE=25
TDS_GROUP_MEMBER=25000
#-----------------------------------------------------
# DB2 BUFFERPOOL (Number of pages)
#-----------------------------------------------------
IBMDEFAULTBP=AUTOMATIC
LDAPBP=AUTOMATIC
#-----------------------------------------------------------------
# System memory allotted to Directory Server Instance (Kilo Bytes)
#-----------------------------------------------------------------
SYSTEM_MEMORY=102417.12
#------------------------------------------------------
# Will be set to True if enough system memory is available to
# the directory instance to make directory caching effective
#------------------------------------------------------
SYS_MEM_AVL=FALSE
#------------------------------------------------------
# Perftune Advance tuning parameters
#------------------------------------------------------
# NEWLOGPATH allows you to specify a string of up to 242 bytes to
# change the location where the log files are stored.
NEWLOGPATH=None
#------------------------------------------------------------------
# DB2 PARAMETER STATUS
# <DB2 parameters>=<Current Value>:<Recommendation>
# Recommendation can be <Not Collected>/<OK>/<Increase>/<Decrease>
#------------------------------------------------------------------
# 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=2000:OK
# 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=2299:Increase
# 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=98:OK
# MAXFILOP specifies the maximum number of file handles that can be open
# for each database agent.
MAXFILOP=Not Collected
# 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=Not Collected
# 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=Not Collected
#-----------------------------------------------------------
# DB2 parameters whose value will be automatically set by
# DB2 self tuning memory manager
# <DB2 parameters>=<Current Value>/<AUTOMATIC>
#-----------------------------------------------------------
# Indicates the amount of storage that is allocated to the lock list.
# There is one lock list per database and it contains the locks held by all
# applications concurrently connected to the database.
LOCKLIST=AUTOMATIC
# Number of I/O servers configuration parameter
NUM_IOSERVER=AUTOMATIC
# Number of asynchronous page cleaners configuration parameter
NUM_IOCLEANER=AUTOMATIC
#-------------------------------------------------------
# DB2 AUTOMATIC PARAMETERS
# <DB2 parameters>=<ON>/<OFF>
#-------------------------------------------------------
# SELF_TUNING_MEM determines whether the memory tuner will dynamically distribute
# available memory resources as required between memory consumers that
# are enabled for self tuning.
SELF_TUNING_MEM=ON
# AUTO_MAINT Automatic maintenance configuration parameter
AUTO_MAINT=ON
# This parameter is the parent of all table maintenance parameters
# (auto_runstats, auto_stats_prof, auto_prof_upd, and auto_reorg).
AUTO_TBL_MAINT=ON
# AUTO_RUNSTATS Automatic table maintenance configuration parameter
AUTO_RUNSTATS=ON
#-------------------------------------------------------
# OLD TDS CACHE PARAMETER ( Prior to last Update Operation )
#-------------------------------------------------------
O_TDS_ENTRY_CACHE=25000
O_TDS_FILTER_CACHE=25000
O_TDS_GROUP_CACHE=25
O_TDS_GROUP_MEMBER=25000
#-------------------------------------------------------
# OLD DB2 PARAMETER VALUE ( Prior to last Update Operation )
#-------------------------------------------------------
O_IBMDEFAULTBP=AUTOMATIC
O_LDAPBP=AUTOMATIC
O_PCKCACHESZ=2299
O_LOGBUFSZ=98
O_MAXFILOP=64
O_CHNGPGS_THRESH=80
O_SORTHEAP=355
O_DBHEAP=2333
O_NEWLOGPATH=None
O_LOGFILSIZ=2000
#-------------------------------------------------------
# INITIAL TUNING PARAMETER VALUE ( Prior to First Update Operation )
#-------------------------------------------------------
I_TDS_ENTRY_CACHE=25000
I_TDS_FILTER_CACHE=25000
I_TDS_GROUP_CACHE=25
I_TDS_GROUP_MEMBER=25000
I_IBMDEFAULTBP=AUTOMATIC
I_LDAPBP=AUTOMATIC
I_PCKCACHESZ=2299
I_LOGBUFSZ=98
I_MAXFILOP=64
I_CHNGPGS_THRESH=80
I_SORTHEAP=355
I_DBHEAP=2333
I_NEWLOGPATH=None
I_LOGFILSIZ=2000