From owner-freebsd-questions Thu Nov 30 13:20: 9 2000 Delivered-To: freebsd-questions@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id D6F4337B401 for ; Thu, 30 Nov 2000 13:19:59 -0800 (PST) Received: from hpbs4894.boi.hp.com (hpbs4894.boi.hp.com [15.8.29.120]) by palrel1.hp.com (Postfix) with ESMTP id 147FB13C1; Thu, 30 Nov 2000 13:19:07 -0800 (PST) Received: from warped (warped.boi.hp.com [15.39.100.73]) by hpbs4894.boi.hp.com with SMTP (8.9.3 (PHNE_18979)/8.8.6 SMKit7.02) id OAA12316; Thu, 30 Nov 2000 14:19:05 -0700 (MST) Message-ID: <001201c05b13$2a65e140$4964270f@boi.hp.com> From: "Jason Sheets" To: , Cc: References: <20001130103627.B22943@HiWAAY.net> <3A269F04.3DEF4C32@urx.com> <00113022083202.01128@web1.tninet.se> Subject: Re: ftp transfer rates on my LAN Date: Thu, 30 Nov 2000 14:19:03 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 Disposition-Notification-To: "Jason Sheets" X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG speedguide.net has multiple patches for windows 95/98/me and 2000. speedguide's primary purpose is to increase download speeds on broadband but the results can also be seen on any high speed network. Jason ----- Original Message ----- From: "Mark Rowlands" To: Cc: Sent: Thursday, November 30, 2000 2:08 PM Subject: Re: ftp transfer rates on my LAN > On Thursday 30 November 2000 19:40, Kent Stewart wrote: > > David Kelly wrote: > > > On Thu, Nov 30, 2000 at 09:33:24AM -0500, bob@sfcei.com wrote: > > > > Just my .02 here. IIRC, Windows seems to max out around 1472 for the > > > > MTU, otherwise there are lots of collisions on the net. I set the MTU > > > > on my FBSD box to 1472 and no collisions. This may affect your > > > > throughput, if only marginally. > > > > > > Ethernet collisions are not bad. Don't sweat 'em until/if they reach > > > 150% to 200%. A 1500 octet packat takes a while to send. But a"collision" > > > happens in the first 64, takes very little wire time. Many NICs do not > > > report these collisions at all. Don't believe I've seen them on 3com > > > NICs I have used. Rather those NICs report *late* collisions which are > > > bad, very bad, indicating a protocol implementation error, hardware > > > failure, or a network which is too long. Yup, the network can get so > > > big the speed of light is no longer fast enough to meet the ethernet > > > timing specs. > > > > > > An analysis I no longer can find the URL for showed a 200% collision > > > rate on 10 Mbps ethernet resulted in an 8% reduction in network > > > capacity. So don't sweat the collisions. > > > > > > In this thread the user has two machines connected point-to-point with > > > a crossed cable. No way for collisions to occur. There might be some > > > advantage to turning on full duplex, which I've never seen > > > auto-negotiated when connected that way, only when connected to a switch > > > which does something to suggest to the machine that full duplex is > > > available. > > > > I haven't measured what the affect is but Window's has a registry key > > called TCPWindowSize on W2K that you can set to 16k and improve > > throughput on files being sent to the Windows machine. I was told that > > their receive windows size is setup to ack/nack records over dialup > > and is really to small for real networks. I know where the key is on > > W2K but not off of my head for the 9x variety. > > > > Kent > > from the horses mouth comes the following > > http://www.microsoft.com/windows95/downloads/contents/wuadmintools/s_wunetwo rkingtools/w95sockets2/default.asp > > the winsock2 patch includes:- > > Support for TCP large windows (TCPLW) and time stamps > Support for selective acknowledgements > Support for fast retransmission and recovery > Support for DHCP release on shutdown > Support for DHCP decline > Support for per-adapter WINS servers > > Win95 is purportedly optimized towards dialup internet connectivity!!!! the > following registry path supposedly fixes this. > > REGEDIT4 > > [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP] > "DefaultRcvWindow"="64240" > "DefaultTTL"="64" > "PMTUDiscovery"=dword:00000001 > "PMTUBlackHoleDetect"=dword:00000000 > > [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0000] > "MaxMTU"="1500" > > [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0001] > "MaxMTU"="1500" > > [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0002] > "MaxMTU"="1500" > > [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0003] > "MaxMTU"="1500" > > [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0004] > "MaxMTU"="1500" > > [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0005] > "MaxMTU"="1500" > > [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0006] > "MaxMTU"="1500" > > [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0007] > "MaxMTU"="1500" > > [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0008] > "MaxMTU"="1500" > > [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0009] > "MaxMTU"="1500" > > > > 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