From owner-freebsd-hackers Mon Jul 19 10:16:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 0254914CB1; Mon, 19 Jul 1999 10:16:25 -0700 (PDT) From: "Jonathan M. Bresler" To: rbezuide@oskar.nanoteq.co.za Cc: vince@venus.GAIANET.NET, sthaug@nethelp.no, tim@storm.digital-rain.com, freebsd-hackers@FreeBSD.ORG In-reply-to: <199907190816.KAA22986@oskar.nanoteq.co.za> (message from Reinier Bezuidenhout on Mon, 19 Jul 1999 10:16:47 +0200 (SAT)) Subject: Re: poor ethernet performance? Message-Id: <19990719171625.0254914CB1@hub.freebsd.org> Date: Mon, 19 Jul 1999 10:16:25 -0700 (PDT) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We have previously done many network performance tests for our > products running on FreeBSD ... > > We have found that when ever there is disk accessing involved, it > is not a good idea to look at the transfer figures. We did tests > with ftp and is was slow (compared to only memory generated data > e.g. ttcp) > > 1. If you want to test the network speed ... use ttcp or something > that generates the data and doesn't read it from disk. > absolutely right. netperf generates its own data on the fly. it does not generate any disk activity. > 2. When doing full-duplex and using fxp cards, stay away from X-over > cables ... use a full-duplex switch etc. ... the fxp cards are not > made to work with X-over cables (as far as I know - ala Intel spec) > note ... only for full-duplex tests. hmm....i have used intel cards on a cross-over cable regularly without any problems whatsoever. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message