Path: utzoo!mnetor!uunet!husc6!mailrus!nrl-cmf!ames!pasteur!ucbvax!CS.BROWN.EDU!jb
From: jb@CS.BROWN.EDU (Jim Bloom)
Newsgroups: comp.sys.encore
Subject: Re: why no inetd ?
Message-ID: <8805031641.AA23695@archer.cs.brown.edu>
Date: 3 May 88 16:41:43 GMT
References: <2986@encore.UUCP>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 20


    Something that will probably be considered before we commit to inetd
    for services like login, telnet, shell, etc, is whether or not there will
    be a performance penalty in single threading the listening end of all those
    services?  This is important for the Multimax, considering that as it
    sits now, rlogind and telnetd can both be accepting a connection at the
    same time.  However, I would probably lay odds that any such performance
    penalty will be insignificant.

Yes, performance will take a slight hit.  The delay should only be about
the same as when telnet or rlogin gets two connection requests at the same
time.  Unless the machine is getting on the order of tens of connection
requests per second (or maybe more), the effect should be unnoticable.
If you look at most machines, I'd say the connection request rate more
likely averages on the order of one per minute (for all services under
inetd).  The burst rate is higher, but I still don't think it is anywhere
near fast enough to cause problems.  The limiting factor here will be
how fast can inetd fork.

					Jim Bloom