*BSD News Article 80594


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!metro!metro!asstdc.scgt.oz.au!nsw.news.telstra.net!act.news.telstra.net!psgrain!usenet.eel.ufl.edu!news-peer.gsl.net!news.gsl.net!portc01.blue.aol.com!news-e2a.gnn.com!howland.erols.net!news.sprintlink.net!news-peer.sprintlink.net!newsfeed.internetmci.com!news-in2.uu.net!twwells!twwells!not-for-mail
From: bill@twwells.com (T. William Wells)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: FreeBSD as news-server??
Date: 12 Oct 1996 14:16:39 -0400
Organization: None, Mt. Laurel, NJ
Lines: 31
Message-ID: <53ona7$69b@twwells.com>
References: <537ddl$3cc@amd40.wecs.org> <53ffcu$ktm@itchy.serv.net> <Dz375G.76v@news2.new-york.net> <Dz67pz.87y@interactive.net>
NNTP-Posting-Host: localhost.twwells.com

In article <Dz67pz.87y@interactive.net>,
Chris Mauritz  <ritz@interactive.net> wrote:
: More RAM.  I like putting 128mb in my news boxes.  It seems
: to work well.

The point is to not swap.

One other detail: programs like expire and expireover are
completely, totally, (and unnecessarily) wasteful of RAM.  Also,
when innd forks, to handle an nnrpd or some types of outgoing
connections, innd memory waste temporarily doubles in size.

Make sure your swap is *huge*. :-)

(INN is, performance- and resource-wise, a piece of garbage. My
version of inn accepts 50% more articles/second and uses like 20%
of the memory. 'Nuff said. No, sorry, I can't hand out the code;
it isn't a simple patch, it's essentially a complete rewrite of
major pieces of the system and the code is not even close to
distribution quality.)

: Faster net connection.  Last I heard, you were using a 56k
: link.  That simply isn't fat enough for a newsfeed.  I'd
: go further and say that you really need at least 128k just
: for news since there's lot's of nntp overhead slop to deal
: with as well.  Last I checked, I was getting roughly 1-1.5g

Check again. :-) Last *I* checked, it was 2.5G/day and you really
want 256k or even 384k. You can *barely* run a non-binary over
56K -- if you batch and compress. Um. That was a few months ago.
Probably isn't true anymore. :-)