Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!wuarchive!kuhub.cc.ukans.edu!anu-news!list
From: munnari!anu.anu.oz.au!gih900@CSC1.ANU.OZ.AU (Geoff Huston)
Newsgroups: news.software.anu-news
Subject: Re: RE: A New Topic -- Tuning News
Message-ID: <9002122346.AA16425@uunet.uu.net>
Date: 13 Feb 90 13:17:28 GMT
Sender: ANU-NEWS Discussion <ANU-NEWS@NDSUVM1.BITNET>
Reply-To: Geoff Huston <munnari!anu.anu.oz.au!gih900@CSC1.ANU.OZ.AU>
Lines: 29

>In article <903.25cdb672@simpact.com>, jeh@simpact.com writes:
>> The thing I'm most unhappy about wrt NEWS performance is the startup time,
>> ie the time from when I type NEWS at the DCL prompt until I see my first
>> unread item or newsgroup directory or whatever.  Once it's started I think
>> the performance is acceptable, except for....
>>
>
>  I agree with this -- especially in light of the fact that NEWS gets
>invoked for *each* batch of news that needs to be added.  I usually
>receive on the order for 100-150 news batches per day which amounts
>to lots of wasted CPU time just in invoking NEWS.
     
You can cut the startup time by tuning NEWS.ITEMS as frequently as possible.
     
Apart from that I'd welcome any code suggestions which can offer tangible
improvements in speed.
     
>> ...the constant returning to the news item directory when it's unnecessary
>> (from my point of view, anyway).
>>
>
>  This is another biggie on my "hit" list.  This is especially
>frustrating when reading news from a 2400 baud line.
     
Again I'd welcome code suggestions here. I have posted on this before, and to
date have received no real suggestions on where improvements could be made.
     
Geoff Huston
gih900@csc.anu.oz.au