On Wed, 09 Nov 2005, Joshua Schmidlkofer wrote:
> Does this mean that those of us using XFS should run some testing as well?
Yes, XFS doesn't journal data in any way, AFAIK. I don't know how one could
go about speeding up fsyncs() with it.
What I *do* know is that I don't trust spools to XFS, b
Yes, on ext3, an fsync() syncs the entire filesystem. It has to, because
all the metadata for each file is shared - it's just a string of
journallable blocks. Similar story with the data, in ordered mode.
So effectively, fsync()ing five files one time each is performing 25 fsync()s.
One fix (
>>> This guy is having a problem with cyrus-imap and ext3 - when multiple
>>> processes are attempting to write to the one filesystem (but not the one
>>> file), performance drops to next to nothing when only five processes are
>>> writing. An strace shows most of the time is being spent in fdatasy
John Madden wrote:
This guy is having a problem with cyrus-imap and ext3 - when multiple
processes are attempting to write to the one filesystem (but not the one
file), performance drops to next to nothing when only five processes are
writing. An strace shows most of the time is being spent in fd
>> This guy is having a problem with cyrus-imap and ext3 - when multiple
>> processes are attempting to write to the one filesystem (but not the one
>> file), performance drops to next to nothing when only five processes are
>> writing. An strace shows most of the time is being spent in fdatasync
>
To: Andrew McNamara <[EMAIL PROTECTED]>
cc: "John Madden" <[EMAIL PROTECTED]>,
info-cyrus@lists.andrew.cmu.edu
Subject: Re: improving concurrency/performance (fwd)
Andrew McNamara <[EMAIL PROTECTED]> wrote:
>
> This guy is having a problem wi
