"Stephen C. Tweedie" wrote:
>
> Try opening the file with open(O_SYNC), and write the data in 128k chunks
> or so. Alternatively call fsync() every so often to force the data to
> disk (though fsync is not particularly efficient on large files with
> 2.2).
>
If you are interested in a more eff
Here are some benchmark data to show the difference my fastsync patch
(posted here a few days ago as "faster fsync and real fdatasync") can
make.
Basically this patch omits a scan through all the cached blocks of a
file
on fsync and it enables fdatasync not to sync the inode if only
mtime/cti
I noticed that sys_fsync can be very slow, because it has to scan all
cached pages of the file (this takes about 1ms/MByte on my dual P3-450).
I wrote a patch that fixes this problem and adds an implementation of
fdatasync (the inode does not get flushed if only mtime/ctime are
changed).
I first
