Date: Mon, 15 Nov 1999 09:54:23 -0600 From: Nathan Kinsman <nathank@mentisworks.com> To: freebsd-questions@freebsd.org Subject: Re: SAMBA / 3.3-Stable / transfer delay Message-ID: <38302CAF.2C7286BC@mentisworks.com> References: <Pine.BSF.4.10.9911151146090.79614-100000@ricardis.ricardis.tudelft.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
I have seen these problems with Samba and FreeBSD since Samba version 2.04. I used to get very good performance, and even used Samba to demonstrate FreeBSD's superiority over Windows NT and Linux for file serving to some clients, but this is not the case anymore. I can get outstanding write performance, utilizing around 70% of my 100 meg ethernet hub by setting the recieve buffer to 262144 (performance starts flattening around a 65k receive buffer though), but I can not get write performance past about 300k, with high delays between packets. Setting any other socket options has not helped. I've also tried compiling with pgcc and egc 2.95.2 with a number of different compile switches, but Samba is not very influenced by compiler choice, the performance varies little. An interesting observation is that Windows NT performance is not nearly as poor, and can write to the FreeBSD server about twice as fast with little delay. The problems seems mostly with FreeBSD and Windows 98 (perhaps 95 as well?). My hard drives bench at 19 megs per sec, so this is not a limiting factor, and I believe the EtherExpress Pro100b driver I'm using is decently stable and tested. Any one able to offer more insight into this problem? I think the Samba team is not going to be much help as I don't think they are very happy with FreeBSD breaking their MSG_WAITALL optimization from 2.0.5. I'd hate to see our platform becoming a poor choice for running Samba when so many businesses are using it. - Nathan Kinsman Rik van Mierlo wrote: > > On Fri, 12 Nov 1999, Edirol wrote: > > > I'm using 3.3-RELEASE with Samba 2.05 (installed from ports) and I notice > > that there's a ~5sec delay in opening a file on the FBSD server from a > > Win98SE machine sometimes. My transfer speeds aren't affected however. > > > > I haven't tried Samba 2.06 yet though. > > > > - Will > > > > ----- Original Message ----- > > From: Marty Cawthon <mrc@ChipChat.com> > > To: <freebsd-questions@FreeBSD.ORG> > > Cc: <argyll@ChipChat.com> > > Sent: Thursday, November 11, 1999 4:21 PM > > Subject: SAMBA / 3.3-Stable / transfer delay > > > > > > > I am experiencing a "one-way delay" in file transfers from Microsoft > > Clients > > > (Windows 95 and Windows NT) to Samba. > > > > > > FreeBSD 3.3-Stable as of Oct 8 1999 > > > samba 2.0.5 installed from the ports collection > > > smb.conf includes this line: > > > socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SENDBUF=16384 > > SO_RCVBUF=16384 > > > (originally it had just 'TCP_NODELAY' > > > but I added the others per suggestions found in on-line resources) > > > > > > Network is a 10/100 Mbps Bay Switch with all below running 100 Mbps > > > ------------------------------------------------------------------------- > > > Client Send 1MB to SAMBA Receive 1MB from SAMBA > > > copy e:\test\file u:\ copy u:\file e:\test > > > ------------------------ ---------------------- ---------------------- > > > Microsoft Windows 95 15 seconds Instantaneous > > > Microsoft Windows NT4 15 seconds Instantaneous > > > IBM OS/2 + TCP/IP 4.1 Instantaneous Instantaneous > > > ------------------------------------------------------------------------- > > > (IBM OS/2 TCP/IP 4.1 is an optional IBM TCP/IP stack for OS/2 > > > which IBM describes as a "BSD 4.3 stack") > > > > > > I had mentioned this at FreeBSDCon, and several people had suggestions, > > > most mentioned the "TCP_NODELAY" option. > > > > > > I still see this delay. > > > Do others run 3.3-Stable and Samba also see this type of delay? > > > Are there other suggestions for solving this trouble? > > > > > > Marty Cawthon > > > ChipChat > > > > The "one-way delay" turns out to be a two-way-delay. I experienced the same > problems, but when I used smbclient to connect to a Windows NT4 box instead > of the other way around, the put command was about 4 times slower than the > get command. So it seems to me that putting a file is slower than getting a > file. I don't know whether this is possible (isn't get the same as put?) but > I hope this gives you another idea as to where to look for the problem. > > -Rik van Mierlo > -rik@ricardis.tudelft.nl > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38302CAF.2C7286BC>