[cvsnt] Re: wnt_fclose and FlushFileBuffers

John Goehringer john.goehringer at agilisys.net
Thu Feb 6 22:14:05 GMT 2003

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

Yes, removing FlushFileBuffers does solve the performance problem.

I saw the most effect on large checkouts - you can 'hear' the difference
in disk activity as the files are written to disk on the client. The server
seems to do the same - I guess from flushing the last accessed time of
the file.

I can get some comparison timings if you like.

John Goehringer

"Tony Hoyle" <tmh at nodomain.org> wrote in message
news:b1ul39$goj$1 at sisko.nodomain.org...
> Tony Hoyle wrote:
> > John Goehringer wrote:
> >
> >> Tony,
> >>
> >>     I'm seeing poor performance on both the client and server
> >> with build 69 compared to build 68 and tracked it down to
> >> the FlushFileBuffers call in win32.c:wnt_fclose.
> >>
> Hmm... seems to be OK now without it.  I'll have to run proper tests
> Presumably if you remove the FlushFileBuffers your speed problems are
> solved?
> Tony

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook