On Sun, Nov 7, 2010 at 4:13 PM, Greg Smith <greg@2ndquadrant.com> wrote:
> Jeff Janes wrote:
>
>> Assuming the ordering is useful, the only way the OS can do as good a
>> job as the checkpoint code can, is if the OS stores the entire
>> checkpoint worth of data as dirty blocks and doesn't start writing
>> until an fsync comes in. This strikes me as a pathologically
>> configured OS/FS. (And would explain problems with fsyncs)
>>
>
> This can be exactly the situation with ext3 on Linux, which I believe is one
> reason the write sorting patch didn't go anywhere last time it came
> up--that's certainly what I tested it on.
Interesting. I think the default mount options for ext3 is to do a
journal sync at least every 5 seconds, which should also flush out
dirty OS buffers, preventing them from building up to such an extent.
Is that default being changed here, or does it simply not work the way
I think it does?
Thanks for the link to the slides.
Cheers,
Jeff