INN not keeping up with incoming news

[bill davidsen]

In article <20010130102134.R6501 at apocalypse.cdsnet.net> you write:

| It's good to see people working on updates, but I'm thinking I'm going
| to have to switch to something else at least for the transit server portion,
| and that's not my first choice.

  Not 2nd or 3rd, but you do what you must.

| I am happy to test patches, and i keep fairly current.
| 
| My systat -netstat output always shows data pending in the queue waiting for
| innd to read it.  I've tried tweaking buffer sizes , I've had feeds
| split up, but it just ain't cutting it...

  I kicked the initial buffer size with limited gain. I raised the
window size to tcp. I locked some stuff in memory. I increased free
system memory, and went into the /proc/sys/net/core and raised some
sizes. Each of which gave incremental gain when I need a factor of four
or so.

  Next - go to the 2.4.1 kernel (or latest, but 2.4.1 has been stable).

  After that - next week I have a patch to do which increases the
priority of file transfer over command reading. If I'm flat out with
what I have I don't want to take more. I expect this to make a huge
change, possibly in the right direction;-)

  Then - unless the threading patches are ready, INN goes. It has many
features I really find useful, but I can't spend all my time trying to
catch up feeds. If I can't get capacity to catch up, I have to do
something else.
-- 
bill davidsen <davidsen at tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.