*BSD News Article 64875


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.telstra.net!act.news.telstra.net!vic.news.telstra.net!news.mira.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!qns3.qns.com!imci4!newsfeed.internetmci.com!news.mathworks.com!zombie.ncsc.mil!cs.umd.edu!newsfeed.gsfc.nasa.gov!kjeffers
From: kjeffers@nastg.gsfc.nasa.gov (Karen Jefferson x2857)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: FreeBSD Losing to Linux - Please Help
Date: 3 Apr 1996 15:18:03 GMT
Organization: NASA Goddard Space Flight Center -- Greenbelt, Maryland USA
Lines: 19
Message-ID: <4ju4rb$67q@post.gsfc.nasa.gov>
NNTP-Posting-Host: nastg.gsfc.nasa.gov
X-Newsreader: TIN [version 1.2 PL2]


We are in the midst of a development project which uses alot of UDP 
and serial communications.

Although our preference had been to use FreeBSD, the UDP
performance was terrible (200 Kbps over Ethernet), and we
kept getting ENOBUF errors  which  makes FreeBSD an unacceptable choice.
Our previous posts for possible parameters to tune didn't
turn up anything helpful, and messages to freebsd.org haven't been
answered yet.

The TCP performance was the same for both Linux and FreeBSD, and UDP
testing on all other platforms in our facility proved okay for Solaris,
SunOS, & SCO.

Is there anything we can do to improve the UDP performance of FreeBSD?
Why does it care about buffering for UDP?  Please respond via email
to tjeffers@nastg.gsfc.nasa.gov.  Thanks.