🚀 go-pugleaf

bruce@sonyd1.Broadcast.Sony.COM (Bruce Lilly) asks:
> INN memory requirements:
> a)      exactly how much is lots''?

A fully runninf "innd" needs a few thousands of pages. On my site
(not yet a full feed), the size seems to stabilize at around 2500 pages
which is 10 Megs.  Being on a 16 Megs system, it mostly gets swapped
out.  On incoming NNTP connections, I have seen around 1000 pages being
loaded.  I also run INN on a 8 Megs Sun 3. Just fine.  My history is
relatively small, around 7 Megs.

Maybe could Rich post UUNET's memory pages occupation of innd regarding
to their history's size which is just in "another dimension" compared to
my 7 Megs.

> c)      does fairly important'' mean that INN will crash and
>        burn if it can't malloc  more than 2.5 MB of VM (e.g.)?

Did anyone try with so little ?

> Does innd have to be running continuously, or can it be run on an
> as-required basis from inetd (suitable for machines with low
> volume feeds and only occasional newsreader connections (nntpd
> can be run from inetd))?

Innd is a permanently running daemon.  But on no NNTP sessions, it's
just swapped out if needed.

INN is doing in one process the job of msgidd + nntpd + relaynews, with
no temporary files, less input-outputs and faster IO operations.

This just improves dramatically the performances on any system and
especially on those with slow IO, such as AIX on rs6k boxes.

The bottlenecks are still the same mainly: forwarding news, news reading
and the way articles are stored on disk.

-- 
Christophe Wolfhugel    |    Email: Christophe.Wolfhugel@grasp.insa-lyon.fr
  "Pour le bien-etre de tous, il est interdit de pisser dans le metro."