On Nov 20, 2007, at 14:57, Pascal Gienger wrote: > Rob Banz <rob@xxxxxxxxxxx> wrote: > >> >> We went through a similar discussion last year in OpenAFS land, and >> came the same conclusion -- basically, if your filesystem is >> reasonably reliable (such as ZFS is), and you can trust your >> underlying storage not to lose transactions that are in-cache >> during a >> 'bad event', the added benefit of fsync() may be less than its >> performance cost. > > Would'nt it be nice to have a configuration option to completely > turn off fsync() in Cyrus? If you want, with a BIG WARNING in the > doc stating NOT TO USE IT unless you know what you doing. :) That's basically what we did with the AFS volserver & fileserver. Oddly, when the patch got integrated into the OpenAFS code, they didn't like the idea of it being an option and made it the default ;) ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html