Slowdown when copying large files (PR#8617)

[Matt JD Aldridge]

> Date: Mon, 27 Jul 1998 10:09:30 -0700
> From: Jeremy Allison <jallison at cthulhu.engr.sgi.com>
> To: peloy at ven.ra.rockwell.com, "samba at samba.anu.edu.au"
> <samba at samba.anu.edu.au>
> Subject: Re: Slowdown when copying large files (PR#8617)
> Message-ID: <35BCB44A.49535E32 at engr.sgi.com>
>
> peloy at ven.ra.rockwell.com wrote:
> >
> > Andrew Tridgell <samba-bugs at samba.anu.edu.au> wrote:
> >
> > > The Windows98 explorer (and possibly other programs)
> incorrectly set the
> > > "sync" bit in write requests to network shares. This
> causes an enormous
> > > slowdown as Samba (quite correctly) does a fsync() on the
> file after each
> > > write. Combine this with the fact that Windows98 explorer
> uses very small
> > > write sizes (around 1.5k) and you get really terrible results.
> >
> > Andrew, but if it is Windows 98 the one that is screwing things up,
> > wouldn't this slowdown be seen when the server is something
> else, like
> > Windows 95/NT, etc.?
> >
>
> Apparently not - according to one of JohnT's technical
> contacts at MS - doing a fsync on a file in NT isn't the
> same as a UNIX fsync, but only *schedules the write to
> be done* !
>
> I will add this option before 1.9.18p9 ships - the only
> question is - should it be on or off by default ?

Is there no way to identify the client as being Win 98 and act
appropriately?  Shame if not.

Cheers,

Matt.
--
Matt JD Aldridge - NEXOR Technical Analyst
Email: mailto:Matt.Aldridge at NEXOR.Com
Phone: +44 (0)115 952 0572 (has voicemail)