At 06:22 PM 2/11/01 -0500, you wrote:
>What does the thread_in setting do and where would it go?
It goes in dnews.conf
thread_in true
It makes dnews use a thread for each incoming stream of news, this
has two advantages, 1), the code has been carefully optimized in this
module to deal with incoming news streams, and 2) the socket reads
are more consistent which prevents the tcpip pipeline stalling due to
small buffer sizes on the transmission end, and 3) it may make use of
cpu which is not being used for anything.
The net result is the incoming feed will be able to go in faster.
You need at least 5.4j7 because this code contained bugs prior to that
version :-)
ChrisP.
>On Mon, 12 Feb 2001 09:55:36 +1300, NetWin Support Auckland
><[EMAIL PROTECTED]> wrote:
>
> >At 09:21 AM 2/11/01 -0500, you wrote:
> >>How come, my dnews processor percentage figure is totally different to
> >>that which the system reports. I just noticed that for the last hour
> >>it's been at 99/99 Busy % on the admin tool. If I look at the NT Task
> >>Manager it's running at around 20%.
> >
> >One is how busy dnews is, the other is how much cpu you are using. If
> dnews is
> >waiting for disks most of the time then cpu use will remain low even though
> >dnews can't 'go any faster'
> >
> >To confuse things further if you have thread_in true and 5.4j7 or later then
> >dnews could use more than 100% due to threading :-)
> >
> >So the difference does indicate your system isn't balanced and maybe
> could be
> >tuned a bit.
> >
> >So if you think you have a performance problem set 'timing true' in
> >dnews.conf, "tellnews reload"
> >and then after running dnews for a few hours send us:
> > dnews.conf
> > newsfeeds.conf
> > tellnews status
> > tellnews stats
> >
> >And we'll check for possible tuning settings you could use.
> >
> > ChrisP.
