On 02/24/2014 01:16 PM, hede wrote:
I'm planning to use 389ds from SD-Card. So I would like to minimise write I/O.
It's absolutely fine if there's only a consistent state saved once a day.
For example via some cronjob running ns-slapd db2archive (which I've done so far).
I do not need any database-logs to have even the last seconds in a disaster recovery.
Any hints to tune it for this use case?
There are files constantly written, AFAIK by the Berkeley DB:
Can I get rid of those files? Move them to a Ram Disk?
You can move them to a Ram Disk.
You can also completely disable durable transactions.
389 users mailing list