Path: utzoo!utstat!news-server.csri.toronto.edu!cs.utexas.edu!samsung!dali.cs.montana.edu!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!caen!stealth
From: stealth@caen.engin.umich.edu (Mike Pelletier)
Newsgroups: news.software.nntp
Subject: Re: How much of a load is nntp?
Message-ID: <1990Nov21.180218.2129@engin.umich.edu>
Date: 21 Nov 90 18:02:18 GMT
References: <1990Nov15.155532.3384@ssd.kodak.com> <1990Nov16.220048.22474@engin.umich.edu> <1990Nov17.054512.13632@maverick.ksu.ksu.edu>
Sender: news@engin.umich.edu (CAEN Netnews)
Distribution: na
Organization: University of Michigan Engineering, Ann Arbor
Lines: 24

In article <1990Nov17.054512.13632@maverick.ksu.ksu.edu>
	brtmac@maverick.ksu.ksu.edu (Brett McCoy) writes:
>
>Something most people forget about here is the memory involved.  Each nntp
>connection requires that an nntpd process be running.  If the client is even
>moderately busy this involves several hundred K worth of memory being devoted
>to the nntpd, which is several hundred K lost to any other process trying to
>run.  

Compile your nntpd with the "-n" option (on a DEC at least) to make the
text portion read-only and shared among all users executing the file.
That way, you will only have one copy of the executable sitting in memory
at any given time, no matter how many users are connecting.  Might also
want to consider setting the sticky bit...

Also, when you're talking about your experience with your NFS/NNTP/etc...
server machine, you're not commenting on the performance load imposed
by nntp connections, but rather on NFS+NNTP+whatever else you have going.

--
	Mike Pelletier - Usenet News Admin & Programmer
"Wind, waves, etc. are breakdowns in the face of the commitment to getting
 from here to there.  But they are the conditions for sailing -- not
 something to be gotten rid of, but something to be danced with."