Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!uunet!asp
From: asp@uunet.uu.net (Andrew Partan)
Newsgroups: news.software.b
Subject: Re: Future of USENET
Message-ID: <1991Jun30.031344.3126@uunet.uu.net>
Date: 30 Jun 91 03:13:44 GMT
References: <1991Jun25.111720.17920@zorch.SF-Bay.ORG> <1991Jun28.211649.20438@visix.com>
Organization: UUNET Communications Services
Lines: 17

In article <1991Jun28.211649.20438@visix.com>, amanda@visix.com (Amanda Walker) writes:
> In article <9197@gollum.twg.com> david@twg.com (David S. Herron) writes:
>    Says the wire will need to handle over 100Kbits-per-second all day long.
> I just wanna see what UUNET would be like at that point...

Well we now have 4 machines handling news - one for all incoming &
outgoing nntp, one for uucp batching, & two to handle compress.  Two for
compress is over kill, but they were just sitting there...

Once I get a news replicator in place (so that I can have the same
article path names on multiple systems), we will be splitting the uucp
batcher into multiple pieces (and getting rid of the uunet!uunet hack in
the Path: that we have now) and then we should be able to scale, at
least as far as news goes.  Scaling uucp (or whatever) is going to take
more work.

	--asp@uunet.uu.net (Andrew Partan)