Xref: utzoo news.software.b:1509 news.software.nntp:56
Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!think!husc6!rutgers!psuvax1!blitz!flee
From: flee@blitz (Felix Lee)
Newsgroups: news.software.b,news.software.nntp
Subject: Re: SPOOLNEWS & nntp
Message-ID: <3744@psuvax1.cs.psu.edu>
Date: 29 Jul 88 00:14:00 GMT
References: <10080@e.ms.uky.edu> <14956@oddjob.UChicago.EDU>
Sender: news@psuvax1.cs.psu.edu
Organization: Penn State University Computer Science
Lines: 16

In <10080@e.ms.uky.edu> David Herron writes:
> It's amazing what you'll do when you're bored.  One afternoon I moved the
> SPOOLNEWS code from inews.c into nntpd to see what sort of effect it would
> have on the system load, it "seems" to help quite a bit.

A better way to spend your time is to fix nntpd so that it doesn't spawn
a new inews every time it receives an article.  But B2.11 inews is going
to fork off a new inews for every article anyway.  This would still be a
slight win, especially if your fork() uses copy-on-write.  Even better
would be C news, which doesn't fork at all.  (What about 3.0?)

But nntpd would have to get the size of the article for #!rnews batches.
You could 1) save the article (either in memory or on disk); 2) have the
sender tell you the size; 3) create a batch that uses delimiters instead
of byte counts.  I like the last option best.
--
Felix Lee	*!psuvax1!flee