Path: utzoo!attcan!uunet!virtech!cpcahil From: cpcahil@virtech.uucp (Conor P. Cahill) Newsgroups: comp.unix.i386 Subject: Re: ESIX woes. (serial performance) Keywords: HDB TCP/IP Message-ID: <1989Nov17.130902.13466@virtech.uucp> Date: 17 Nov 89 13:09:02 GMT References: <612@aablue.UUCP> <6965@ficc.uu.net> <862@pmafire.UUCP> Organization: Virtual Technologies Inc. Lines: 36 In article <862@pmafire.UUCP>, dave@pmafire.UUCP (Dave Remien) writes: > In article <1989Nov15.133059.3330@virtech.uucp> cpcahil@virtech.uucp (Conor P. Cahill) writes: > >In article <6965@ficc.uu.net>, peter@ficc.uu.net (Peter da Silva) writes: > >> [serial port performance really amazingly bad with TCP up] > >> > >> With Belltech/Intel V.3.2u, with Lachman TCP/IP: when I have TCP running > >> the performance of the serial port drops dramatically, and I get about > >> 1 in 50 characters lost even at typing speeds. > > > [Conor say 386/IX is similar] I did not say 386/ix was similar. I said: I am running 386/ix with TCP, NFS, X, etc. and have no problems with serial port performance with the networking up or not. I do have an intelligent serial port card which may be the reason. Which in other words says that I do not have the same problem. > I'm running Bell Tech 3.2 (NOT 3.2u, I'm waiting for that) with Lachman > TCP/IP, NFS, X and both a regular serial port and a Bell Tech ACE card; > I have yet to see any slowdown yet that can't be attributed to a 16MHz > '386 and only 4 megs of RAM. I've got an ENET586 card, for what it's > worth. However both my system and yours use an intelligent serial card for serial communications and this may be the key. The original posters did not indicate the kind of serial port they were using, but I would bet that it is the standard dump port. -- +-----------------------------------------------------------------------+ | Conor P. Cahill uunet!virtech!cpcahil 703-430-9247 ! | Virtual Technologies Inc., P. O. Box 876, Sterling, VA 22170 | +-----------------------------------------------------------------------+