Path: utzoo!utstat!news-server.csri.toronto.edu!math.lsa.umich.edu!zaphod.mps.ohio-state.edu!wuarchive!udel!haven!decuac!hussar.dco.dec.com!mjr
From: mjr@hussar.dco.dec.com (Marcus J. Ranum)
Newsgroups: news.software.nntp
Subject: Re: How much of a load is nntp?
Message-ID: <1990Nov18.035402.11348@decuac.dec.com>
Date: 18 Nov 90 03:54:02 GMT
References: <1990Nov15.155532.3384@ssd.kodak.com> <1990Nov16.220048.22474@engin.umich.edu> <1990Nov17.054512.13632@maverick.ksu.ksu.edu>
Sender: news@decuac.dec.com (Network News)
Organization: Digital Equipment Corp., Washington Ultrix Resource Center
Lines: 21

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.

	I assume you don't waste any of your memory with abominations like
X-window, then. :)

	Hmmm... if your system is groaning from too many read-only nntp
connections from rrn, I suppose you could switch to reading articles via
NFS. I doubt you'd save much, though.

mjr.
-- 
"When choosing between two evils, give preference to the council of your
tummy over that of your testes. The history of mankind is full of disasters
that could have been averted by a good meal, followed by a nap on the couch."
		-Me, as explained to me by my wife's cat Strummer.