Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!decvax!ucbvax!YALE.ARPA!LEICHTER-JERRY From: LEICHTER-JERRY@YALE.ARPA.UUCP Newsgroups: mod.computers.vax Subject: Re: DECserver jerky output Message-ID: <8612070806.AA10598@ucbvax.Berkeley.EDU> Date: Sun, 7-Dec-86 03:06:50 EST Article-I.D.: ucbvax.8612070806.AA10598 Posted: Sun Dec 7 03:06:50 1986 Date-Received: Sun, 7-Dec-86 05:13:33 EST Sender: daemon@ucbvax.BERKELEY.EDU Reply-To:Organization: The ARPA Internet Lines: 29 Approved: info-vax@sri-kl.arpa A quick puzzle. I've connected our only DECserver-200, and I've noticed the output from some programs is very jerky (at 9600 baud). I've left most of the server parameters alone. Reducing the circuit timer from 80 to 40 ms does not help. The server is connected via DELNI to what must be the least-loaded ethernet cable in the world. Error counts are very low over a period of several weeks, so there is apparently no physical reason for this. There is no lost data as far as I can see. ... I believe SOME "jerkiness" is normal - the LAT protocol IS a packetizing protocol, and the human eye seems to be pretty sensitive to this kind of effect. I've been using LAT lines on and off for long enough now that I don't notice any more. As I recall, you stop noticing after a week or so. (Further, when I use a LAT line after several weeks of NOT using one, I don't notice the effect either.) The actual effect on throughput of the "jerkiness" is minimal. Also, loading on the Ethernet will have no effect on this phenomenon - it won't get any worse until you are bringing your Ethernet to the point of collapse. My advice: Give it a week of steady use. If it still bothers you, check out the system more closely, as there really MAY be something wrong. BTW, note that decreasing the circuit timer value as you did will increase loading on the host - it will just about double it. Probably not worth worrying about, but worth being aware of. -- Jerry -------