[Info-vax] SAMBA really sloooow on OVMS Integrity. Any Ideas????
David Mathog
dmathog at gmail.com
Tue Aug 17 14:38:42 EDT 2010
On Aug 17, 7:47 am, Len Whitwer <l... at psds.com> wrote:
> As I posted earlier when transfering a large file from windows to
> Samba it takes about a minute to even start moving the file (don't
> know what's going on) where advanced server starts right away. It also
> takes 50% longer in the transfer time once Samba starts writing data.
Had a similar problem with long delays with roaming profiles on W7 to
Samba (on Linux). To solve it turned on logging
for netlogon on the Windows machine and ran wireshark there too to
catch all the packets. It turned out that W7 was
pinging the server to "see if it was fast", but of course, the
server's firewall was dropping all
ping packets so it took forever for this test to time out.
Not saying this is what you are seeing, but it wouldn't hurt to see if
the client can ping the server.
I also recall an issue where Windows machines would attempt an http
connection (port 80) before starting an SMB transfer. It is a long
story, see here: http://www.mail-archive.com/samba@lists.samba.org/msg46161.html
Failing that, do the slow operation with the logs turned on, then
concatenate the two logs, sort by time, and look through it.
If my experience is any guide, you will find a 1 minute gap where the
W7 machine sends something, perhaps repeatedly,
and the server does not send back what it is expecting.
As others have said, on the VMS end file high water marking will
definitely slow things down. If you have access to a linux
Samba server, it would be good to see what sort of performance you see
there, just to see how much of this is a VMS problem and
how much a Samba problem.
Regards,
David Mathog
More information about the Info-vax
mailing list