Miscellaneous Tuning Tips486 Red Hat Directory Server Administrator’s Guide • May 2005Specifying Transaction BatchingTo improve update performance when full transaction durability is not required,you can use the nsslapd-db-transaction-batch-val attribute to specify howmany transactions will be batched before being committed to the transaction log.Setting this attribute to a value of greater than 0 causes the server to delaycommitting transactions until the number of queued transactions is equal to theattribute value. For transaction batching to be valid, thensslapd-db-durable-transaction attribute must be set to on.To specify or modify transaction batching while the server is running, use theldapmodify command-line utility to add thensslapd-db-transaction-batch-val attribute to the cn=config,cn=ldbmdatabase,cn=plugins,cn=config entry.For more information on the syntax and values of thensslapd-db-transaction-batch-val attribute, refer to the Red Hat DirectoryServer Configuration, Command, and File Reference. For instructions on usingldapmodify, refer to “Adding and Modifying Entries Using ldapmodify,” onpage 58.Miscellaneous Tuning TipsThis section provides you with some performance related tips and concepts youought to remember.Avoid Creating Entries Under the cn=config Entry inthe dse.ldif FileThe cn=config entry in the simple, flat dse.ldif configuration file is not storedin the same highly scalable database as regular entries. As a result, if manyentries, particularly entries that are likely to be updated frequently, are storedunder cn=config, performance will probably suffer.Although we recommend you do not store simple user entries under cn=configfor performance reasons, it can be useful to store special user entries such as theDirectory Manager entry or Replication Manager (supplier bind DN) entry undercn=config, as this allows you to centralize configuration information.
