Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!nike!topaz!hedrick
From: hedrick@topaz.RUTGERS.EDU (Charles Hedrick)
Newsgroups: net.unix-wizards,net.lan
Subject: Re: CPU usage of telnetd
Message-ID: <4578@topaz.RUTGERS.EDU>
Date: Fri, 14-Mar-86 16:27:08 EST
Article-I.D.: topaz.4578
Posted: Fri Mar 14 16:27:08 1986
Date-Received: Sat, 15-Mar-86 22:41:48 EST
References: <10620@amdcad.UUCP>
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 15
Xref: watmath net.unix-wizards:17222 net.lan:1349

The vendor is right.  Telnetd is a pig.  There are some things known
that will speed it up a bit.  If you are using vanilla 4.2, there are
some patches to the pty code that will speed up pty's a lot.  But even
with those patches, telnetd can use a fair amount of CPU time.
Fortunately, in practice people don't sit there typing out files at
9600 baud.  So things aren't as bad as they could be.  I'd try to get
an estimate of the amount of terminal output you do during you peak
load period, and see whether the CPU use is worth attacking.  I could
certainly imagine situations where an Ethernet interface that looks
like a DMF would be a great idea.  Actually, I'd rather see somebody
fix telnetd.  I have talked with people who know the terminal code,
and they conclude that a couple of days work could improve performance
dramatically.  But I can't get them to do it.  grrrrr.......  I have
thought of doing it myself, but it would take me an order of magnitude
longer to do it than a real kernel wizard.