Description of problem: Even when there have been no logging activity, ns-slapd forces a checkpoint, generating unnecessary disk traffic. Version-Release number of selected component (if applicable): 1.2.5 How reproducible: Always Steps to Reproduce: 1.On a quiescent system do "pidstat -C ns-slapd -d 60" Actual results: Disk writes are reported Expected results: No disk writes Additional info: Also "ls -lrt /var/lib/dirsrv/slapd-<server>/db" shows the log file and the __ db.nnn files regularly being updated. This is apparently due to checkpoint being called (in db_layer.c:dblayer_txn_checkpoint()) with the DB_FORCE option. Is there any reason to force these checkpoints? I am using the server for user data (uid/gid etc) but not passwords (because I'm using kerberos for that). The ldap data hardly ever changes and I'd like to let the disks spindown in quiet times. An option, at least, to not force checkpoints would be nice.
There are at least two parameters that could help you : nsslapd-db-checkpoint-interval and nsslapd-db-durable-transactions Their descriptions are here : http://www.redhat.com/docs/manuals/dir-server/ag/8.0/Tuning_DS_Performance-Tuning_Database_Performance.html#Tuning_Database_Performance-Changing_the_Database_Checkpoint_Interval http://www.redhat.com/docs/manuals/dir-server/ag/8.0/Tuning_DS_Performance-Tuning_Database_Performance.html#Tuning_Database_Performance-Disabling_Durable_Transactions
Upstream ticket: https://fedorahosted.org/389/ticket/84