#
# DB_CONFIG file for example database
#
# IMPORTANT
# Changes will automatically take effect after slapd is restarted.
# Optionally, the db_recover command can be run manually while slapd
# is stopped.
#
# Cache Size
# Ideally the cache size should be set large enough to hold the entire
# database. This is often not practical, so a good rule of thumb is to
# specify a cache size equal to half the amount of physical memory in the
# system. The syntax of this parameter is:
#	set_cachesize <GBytes> <Bytes> <Segments>
# For additional information on selecting a cache size, see:
# http://www.sleepycat.com/docs/ref/am_conf/cachesize.html
set_cachesize	0	26214400	0

#
# Database Flags
# The DB_LOG_AUTOREMOVE flag, if set, will cause Berkeley DB to
# automatically remove log files that are no longer needed. Automatic log
# file removal is likely to make catastrophic recovery impossible, so only
# use this if you make routine full backups of the LDAP data. An alternative
# to this flag is to call the db_archive command from cron. See the
# db_archive documentation for additional information.
#set_flags       DB_LOG_AUTOREMOVE

#
# Log File Max Size
# The log file max size determines the point at which log files are rotated.
# A good value for this setting is 10 MB.
set_lg_max	10485760

#
# Log Buffer Size
# The log buffer size should be set to about one fifth the size of the max
# log file size.
set_lg_bsize	2097152

#
# Log File Directory
# The log files are written to continuously during ldap write operations.
# This will cause a large number of disk seek operations to take place as
# the system writes to both the database and log files, and  write
# performance will be significantly reduced. It is therefore STRONGLY
# recommended that the log file directory be placed on a different disk
# drive than the datbase files.
# Note also that each database must have its own log directory- different
# databases cannot share the same log directory.
#set_lg_dir	"/var/symas/openldap-logs/example"

# 
# Mutex Alignment, Berkeley DB 4.4 and Later
# Set the alignment of mutexes, in bytes. It is sometimes advantageous to
# align mutexes on specific byte boundaries in order to minimize cache line
# collisions. At the present time the only architecture known to benefit from
# this setting is the ia64.
# WARNING:
# Use this setting only in conjunction with careful benchmarking, as it
# can have disastrous effects on performance if improper values are selected.
# For additional information, see:
# http://www.sleepycat.com/docs/api_c/mutex_set_align.html
#mutex_set_align	128
