Database Plug-in AttributesChapter 3 Plug-in Implemented Server Functionality Reference 169nsslapd-db-spin-countSpecifies the number of times that test-and-set mutexes should spin withoutblocking.nsslapd-db-transaction-batch-valSpecifies how many transactions will be batched before being committed. You canuse this attribute to improve update performance when full transaction durabilityis not required. This attribute can be dynamically modified using ldapmodify. Forfurther information on modifying this attribute, see chapter 14, “Tuning DirectoryServer Performance,” in the Red Hat Directory Server Administrator’s Guide.If you do not define this attribute or set it to a value of 0, transaction batching willbe turned off, and it will be impossible to make remote modifications to thisattribute via LDAP. However, setting this attribute to a value greater than 0 causesthe server to delay committing transactions until the number of queuedtransactions is equal to the attribute value. A value greater than 0 also allows youto modify this attribute remotely via LDAP. A value of 1 for this attribute allowsyou to modify the attribute setting remotely via LDAP but results in no batchingbehavior. A value of 1 at server startup is therefore useful for maintaining normaldurability while also allowing transaction batching to be turned on and offremotely when desired. Remember that the value you choose for this attribute mayrequire you to modify the nsslapd-db-logbuf-size attribute to ensure sufficientlog buffer size for accommodating your batched transactions.Also, the nsslapd-db-transaction-batch-val attribute is only valid if thensslapd-db-durable-transaction attribute is set to on.Default Value: 8KBSyntax: IntegerExample: nsslapd-db-page-size: 8KBEntry DN: cn=config,cn=ldbm database,cn=plugins,cn=configValid Range: 0 to 2^31-1Default Value: 0Syntax: IntegerExample: nsslapd-db-spin-count: 0
