Very bad performance when copying large files from windows to
Christopher R. Hertel
crh at umn.edu
Fri Apr 12 10:11:02 GMT 2002
> "Esh, Andrew" wrote:
> I also have a lot of experience with Win98. There is a performance
> problem which is difficult to produce, but large files should still
> be copied, albeit slowly. To avoid the performance problem I am
> speaking of, make sure you mount the share using the IP address of
> the host, and not its name.
Is this the 'rabbit pellet' transfer we dug into a while back?
If so, using security=server should also be avoided to avoid the
The problem in this case (for the rest of our viewers) is that Windows
Explorer (the GUI) detects subtle timing delays and will slow itself
down. It sends the file using small packets, sends a flush after each
packet, and requires an ACK after each write and each flush.
If this is the behavior that is being seen then I don't think we have a
solution for it other than avoiding security=server and, as Andrew
explained above, connecting to the share using the IP address. You
could also shake bones and burn tana leaves... It's a wierd problem.
Microsoft did put out a fix for this...but those who tried it had worse
results. I can't seem to find the KB article any more, but if I recall
correctly it said that the change to using small packets with a flush in
between was to accomodate network links via satellite. (!?)
Christopher R. Hertel -)----- University of Minnesota
crh at nts.umn.edu Networking and Telecommunications Services
More information about the samba-technical