Xref: utzoo tor.news:131 ont.uucp:373
Path: utzoo!mnetor!spectrix!tmsoft!mason
From: mason@tmsoft.UUCP (Dave Mason)
Newsgroups: tor.news,ont.uucp
Subject: Re: news
Message-ID: <277@tmsoft.UUCP>
Date: 12 Feb 88 02:13:57 GMT
References: <8802050452.AA03771@gpu.utcs.toronto.edu> <314@yunexus.UUCP> <584@ncrcan.Toronto.NCR.COM> <440@spectrix.UUCP>
Reply-To: mason@tmsoft.UUCP (Dave Mason)
Followup-To: tor.news
Distribution: ont
Organization: TM Software Associates, Toronto
Lines: 22

In article <440@spectrix.UUCP> clewis@spectrix.UUCP (Chris R. Lewis) writes:
+----
|In article <584@ncrcan.Toronto.NCR.COM> brian@ncrcan.Toronto.NCR.COM (Brian Onn) writes:
|>We can and are getting more disks, but that's not a solution.  Is this news
|>explosion a passing fad? or is it to be expected again?
|
|I'm wondering whether we're getting some sort of positive feed-back loop
|around here someplace.  There may be some idiosyncrasy with the batch 
|throttles being used that might be causing this.  Henry once suggested the same.
|
|Particularly this last flood.  Eg: lsuc was merrily taking 900K to 1700K
|bytes per day from utzoo for a long period, it abruptly went over 3 megabytes 
|for several days, then dropped back down to 300K.  And is now starting
|to settle out again.
+----
In this case, there were many articles with posting dates >12 days
old.  Therefore I presume it was a large pile of news that got stalled at
?mnetor? (maybe they ran out of disk space, as they are running the throttled
batcher they could have produced this problem - ron?), rather than a feedback
loop.

But next time? who knows?	../Dave