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. :) Pascal (in train of reconfiguring our SAN to make more cyrus checks) PS: Putting deliver.db on tempfs seems to be a nice idea, but in current cyrus code you may not give extra paths to single cyrus databases. Our actual deliver.db on one machine is ca 600 MB tall, so it won't be of any problem to store it completely on tmpfs. ---- 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
